Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc07fb212d598ef8b3b8124090b2d0e94cd0ad22b6e4552f26c97313f21215c0

Tx prefix hash: 39b84c152835ae26fe648f2e61a2094360024b928f2ceb90d67e2bc76c4006fe
Tx public key: 39a0a42d342a0b7548b55c02e384f058d1821142acdbc88a0571cac76ab548e8
Timestamp: 1704321070 Timestamp [UCT]: 2024-01-03 22:31:10 Age [y:d:h:m:s]: 01:312:02:02:19
Block: 927582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481863 RingCT/type: yes/0
Extra: 0139a0a42d342a0b7548b55c02e384f058d1821142acdbc88a0571cac76ab548e802110000000639e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40993f911fa1ee9004a12f73fb00bdafb249230fd90b77481ee626ae51b1c16a 0.600000000000 1385418 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": 927592, "vin": [ { "gen": { "height": 927582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40993f911fa1ee9004a12f73fb00bdafb249230fd90b77481ee626ae51b1c16a" } } ], "extra": [ 1, 57, 160, 164, 45, 52, 42, 11, 117, 72, 181, 92, 2, 227, 132, 240, 88, 209, 130, 17, 66, 172, 219, 200, 138, 5, 113, 202, 199, 106, 181, 72, 232, 2, 17, 0, 0, 0, 6, 57, 225, 213, 211, 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