Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72694f158cae595e7ebc7476b5e1028fa6cb8711953eb9c5e1cf68ec19a99dbd

Tx prefix hash: 3a8e7777dba13c77ecd0aefc4fb75bfac2d9bd431a8113cd1cd6d490be557db4
Tx public key: d0f8fea93f9b50c232b982c675b66826f83c84bbbaf3c6830039df44d2e42e21
Timestamp: 1708551524 Timestamp [UCT]: 2024-02-21 21:38:44 Age [y:d:h:m:s]: 01:077:16:37:31
Block: 962639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316569 RingCT/type: yes/0
Extra: 01d0f8fea93f9b50c232b982c675b66826f83c84bbbaf3c6830039df44d2e42e210211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600500000000 dcy

stealth address amount amount idx
00: ec6ed27f49506d82ff9053aa61e66755bab1757be22e6a95be98f75641dd0aa4 0.600500000000 1422302 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": 962649, "vin": [ { "gen": { "height": 962639 } } ], "vout": [ { "amount": 600500000, "target": { "key": "ec6ed27f49506d82ff9053aa61e66755bab1757be22e6a95be98f75641dd0aa4" } } ], "extra": [ 1, 208, 248, 254, 169, 63, 155, 80, 194, 50, 185, 130, 198, 117, 182, 104, 38, 248, 60, 132, 187, 186, 243, 198, 131, 0, 57, 223, 68, 210, 228, 46, 33, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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