Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d403922f0b6c94fc56289379651b62106253609c9c61d05dec20a2d8fbea7628

Tx prefix hash: eb83b4eb58c1c83df1661202851e9b4dce781167ec664144dd76c305e9643624
Tx public key: a74069bac9e1be9840d1ae17ebe2fc6d77913958aa6a85a067e5e4fb3a5b7818
Timestamp: 1724830757 Timestamp [UCT]: 2024-08-28 07:39:17 Age [y:d:h:m:s]: 00:257:04:34:37
Block: 1097601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183700 RingCT/type: yes/0
Extra: 01a74069bac9e1be9840d1ae17ebe2fc6d77913958aa6a85a067e5e4fb3a5b781802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 574597b1aac5fdc942f9f02fbfab456cb6c856d1a19e025b9cd492df97f310cb 0.600000000000 1573016 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": 1097611, "vin": [ { "gen": { "height": 1097601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "574597b1aac5fdc942f9f02fbfab456cb6c856d1a19e025b9cd492df97f310cb" } } ], "extra": [ 1, 167, 64, 105, 186, 201, 225, 190, 152, 64, 209, 174, 23, 235, 226, 252, 109, 119, 145, 57, 88, 170, 106, 133, 160, 103, 229, 228, 251, 58, 91, 120, 24, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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