Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6354d6300e7ef80569d7fdd17ced5001bedd6658f1cd4ea159d32531b83bda59

Tx prefix hash: 8e5e7f7aca375c4f6e222eb8954ffa22e2cdafca74f5d70f351567c4ca7a5e0a
Tx public key: 5e2c5013eba8dc63986a58fed5e31ddd60a07ea3e016414636d7ad71f5c9bdf7
Timestamp: 1710096309 Timestamp [UCT]: 2024-03-10 18:45:09 Age [y:d:h:m:s]: 01:052:16:48:53
Block: 975458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298668 RingCT/type: yes/0
Extra: 015e2c5013eba8dc63986a58fed5e31ddd60a07ea3e016414636d7ad71f5c9bdf702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36badf5d2273ef294ca9eff088e9f19dd61a5610ac0b99e7ac56bc3c75d640c9 0.600000000000 1435429 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": 975468, "vin": [ { "gen": { "height": 975458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36badf5d2273ef294ca9eff088e9f19dd61a5610ac0b99e7ac56bc3c75d640c9" } } ], "extra": [ 1, 94, 44, 80, 19, 235, 168, 220, 99, 152, 106, 88, 254, 213, 227, 29, 221, 96, 160, 126, 163, 224, 22, 65, 70, 54, 215, 173, 113, 245, 201, 189, 247, 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