Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62b4465911696907f2c4b8cb3427af3fbb2e7350889129d06e11293f1974c271

Tx prefix hash: f143720a6394e2d0e7a1d7e047f97ca60c8f6d2ee2761967058439dc5d3a6d2a
Tx public key: 27fe556bef9b035f98f82a206e0bc112198e7ab9edcb70d64ff2ec4a143ab156
Timestamp: 1710838051 Timestamp [UCT]: 2024-03-19 08:47:31 Age [y:d:h:m:s]: 01:023:18:01:51
Block: 981620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277941 RingCT/type: yes/0
Extra: 0127fe556bef9b035f98f82a206e0bc112198e7ab9edcb70d64ff2ec4a143ab15602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff896a1858012ce1d16969b30fbff3cf891a01aa528aa2a51d7e92bccbece045 0.600000000000 1441717 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": 981630, "vin": [ { "gen": { "height": 981620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff896a1858012ce1d16969b30fbff3cf891a01aa528aa2a51d7e92bccbece045" } } ], "extra": [ 1, 39, 254, 85, 107, 239, 155, 3, 95, 152, 248, 42, 32, 110, 11, 193, 18, 25, 142, 122, 185, 237, 203, 112, 214, 79, 242, 236, 74, 20, 58, 177, 86, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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