Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bb0662651eb86c5f7fd89984b37f3a143d8361eb3d54598563557717badbf310

Tx prefix hash: 880e91e4bb6145046805b4d2877d4f3b26adc8fb26df0f081b17e716aeef4b3c
Tx public key: 39b5abf3b9785be76deb9dbba334b7b54f69a47941100b3d4dfbfefb0fcc27ae
Timestamp: 1704697829 Timestamp [UCT]: 2024-01-08 07:10:29 Age [y:d:h:m:s]: 01:090:06:57:49
Block: 930675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325643 RingCT/type: yes/0
Extra: 0139b5abf3b9785be76deb9dbba334b7b54f69a47941100b3d4dfbfefb0fcc27ae0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fe07701c0bf34a5daf07cd7a412e399e59bedcd44867b61153b1dfd50fbbc86 0.600000000000 1388561 of 15

Check which outputs belong to given Dinastycoin 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 Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-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



{ "version": 2, "unlock_time": 930685, "vin": [ { "gen": { "height": 930675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fe07701c0bf34a5daf07cd7a412e399e59bedcd44867b61153b1dfd50fbbc86" } } ], "extra": [ 1, 57, 181, 171, 243, 185, 120, 91, 231, 109, 235, 157, 187, 163, 52, 183, 181, 79, 105, 164, 121, 65, 16, 11, 61, 77, 251, 254, 251, 15, 204, 39, 174, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8