Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca8d60de04a021637808a81dcdb449b19e38da3d616a7fe9d3c14418b733f13e

Tx prefix hash: 53a243d5fde189910d4e716adf47b014c4f46a0d33862d6b6733f2f4864a8e94
Tx public key: 304e3a64e94cc36019f60abc64e4222a444dbec9e8899e8433a1dc2ffa235f67
Timestamp: 1713681873 Timestamp [UCT]: 2024-04-21 06:44:33 Age [y:d:h:m:s]: 00:348:14:37:21
Block: 1005167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249218 RingCT/type: yes/0
Extra: 01304e3a64e94cc36019f60abc64e4222a444dbec9e8899e8433a1dc2ffa235f670211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 978425324ffda8fdfb5a9dbbb648fdf88c429691608d065e1c988d54e6f98b41 0.600000000000 1465747 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": 1005177, "vin": [ { "gen": { "height": 1005167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "978425324ffda8fdfb5a9dbbb648fdf88c429691608d065e1c988d54e6f98b41" } } ], "extra": [ 1, 48, 78, 58, 100, 233, 76, 195, 96, 25, 246, 10, 188, 100, 228, 34, 42, 68, 77, 190, 201, 232, 137, 158, 132, 51, 161, 220, 47, 250, 35, 95, 103, 2, 17, 0, 0, 0, 3, 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