Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1bd6d793cbab1f44263a4759cace237b7337d402b2776c34be3c8fc781e638b

Tx prefix hash: 27c2267f0c9d64c3c7d2d3d2c250da067f8c40d0e5b43fdc2a6df263c0744601
Tx public key: 701ebf450cc2af6a04c7e0be45d50b1f9501ef876754a713053e3fb61bc43774
Timestamp: 1580265290 Timestamp [UCT]: 2020-01-29 02:34:50 Age [y:d:h:m:s]: 05:036:07:03:46
Block: 54473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1177394 RingCT/type: yes/0
Extra: 01701ebf450cc2af6a04c7e0be45d50b1f9501ef876754a713053e3fb61bc4377402110000000149b77a3d000000000000000000

1 output(s) for total of 405.050492542000 dcy

stealth address amount amount idx
00: c4b7d03ac5427e5d5816afac0287f8179e1c3ed38d1b28b19c685767c0c3a704 405.050492542000 100870 of 0

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": 54483, "vin": [ { "gen": { "height": 54473 } } ], "vout": [ { "amount": 405050492542, "target": { "key": "c4b7d03ac5427e5d5816afac0287f8179e1c3ed38d1b28b19c685767c0c3a704" } } ], "extra": [ 1, 112, 30, 191, 69, 12, 194, 175, 106, 4, 199, 224, 190, 69, 213, 11, 31, 149, 1, 239, 135, 103, 84, 167, 19, 5, 62, 63, 182, 27, 196, 55, 116, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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