Bixbite Blockchain Explorer

Tx hash: 60ac7ed1acc0196ca91413503d5fc93cfef284e394787acc0bc14915ea369148

Tx public key: d3cee1d34b390cdce0e6cbf4033fe72ce6f0add00dc58d281c424dae2280bdbd
Timestamp: 1539362859 Timestamp [UCT]: 2018-10-12 16:47:39 Age [y:d:h:m:s]: 00:060:01:38:19
Block: 96270 Fee (per_kB): 0.0010 (0.0001) Tx size: 18.9688 kB
Tx version: 2 No of confirmations: 50380 RingCT/type: yes/2
Extra: 01d3cee1d34b390cdce0e6cbf4033fe72ce6f0add00dc58d281c424dae2280bdbd

3 output(s) for total of ? bxb

stealth address amount amount idx
00: 90ae9b7139484642f028b70a7042d60a685988e416a3ccb1c1dfb5777addc399 ? 323297 of 457479
01: 26e7a30f01bcbcacaf7d47276a038f65a2c2d775e06270bdeb157b91867ac76b ? 323298 of 457479
02: 6fee5e237c3a5956e5ecc3200ccd439a6b72283e75181677ac573be61a55559e ? 323299 of 457479

Check which outputs belong to given Bixbite address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Bixbite in this transaction

Tx private key can be obtained using get_tx_key command in Bixbite-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



2 input(s) for total of ? bxb

key image 00: 13a2125fb7abf8eec87eed32b49fcfc8496c608e9eb500b5461035a5cd3045b1 amount: ?
ring members blk
- 00: 5dcef9cc285dfbfc308a48487a70a542b01d4e9de756ed8d898be7ee787cf8c5 00077083
- 01: df718abbe66d4ee4489c050b01765cd6770a32bf224ee369e920092b4c741d51 00096067
key image 01: 9e504cf80a2ba74066089912dfd5261a80857dbcfa3fe94d506a356dbcaac2e8 amount: ?
ring members blk
- 00: bc6566586caf3e91eeb3196e045b04f2a01cafaa3ed7280eeae8ee5cef79bb60 00080918
- 01: a60f573e19b4e03cdac80b84930dfb76ccb6e72480f7fcb52229fe793ce4971a 00096057
More details
source code | explorer version (api): master-2018-05-06-9ea9556 (1.0) | Bixbite version: Violet Claim