Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d0de05911a0290bc385b74a49e84c8e90654f0b69fec2d1d39522e847e3212d

Tx prefix hash: af9de70d25bdb56a7dd03d6c97f693f95a1a1c04a362b4d91ef6e8769de1c777
Tx public key: 38bc567606fa3e90eaa3b086ce387a68a379cf92bea99f59053df621d9afb855
Timestamp: 1720728297 Timestamp [UCT]: 2024-07-11 20:04:57 Age [y:d:h:m:s]: 01:120:00:51:22
Block: 1063600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344299 RingCT/type: yes/0
Extra: 0138bc567606fa3e90eaa3b086ce387a68a379cf92bea99f59053df621d9afb855021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bad6dbca4f7422e002f0db0ca24c8c113537a75d3fd36a6e785acdbc9d988d5 0.600000000000 1534117 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": 1063610, "vin": [ { "gen": { "height": 1063600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bad6dbca4f7422e002f0db0ca24c8c113537a75d3fd36a6e785acdbc9d988d5" } } ], "extra": [ 1, 56, 188, 86, 118, 6, 250, 62, 144, 234, 163, 176, 134, 206, 56, 122, 104, 163, 121, 207, 146, 190, 169, 159, 89, 5, 61, 246, 33, 217, 175, 184, 85, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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