Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5282013da98991c1d60a21aeb89afdf0578ff86d28e2122a735f1a7297ea1294

Tx prefix hash: ffd23fae362550a87041373af9f213604c24d85f5e8c8ba2ed3893dca657e91e
Tx public key: 7446bb60b4de250d7ee8f939acc23c8d2d5b963f3cfc3f1354dd2749ec4d8ff7
Timestamp: 1748913602 Timestamp [UCT]: 2025-06-03 01:20:02 Age [y:d:h:m:s]: 00:169:12:48:31
Block: 1296717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118854 RingCT/type: yes/0
Extra: 017446bb60b4de250d7ee8f939acc23c8d2d5b963f3cfc3f1354dd2749ec4d8ff7021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a8750a3a93de78aa387be5c37df586b72c50bb4339d28a94473717fb510e6cc 0.600000000000 1784232 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": 1296727, "vin": [ { "gen": { "height": 1296717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a8750a3a93de78aa387be5c37df586b72c50bb4339d28a94473717fb510e6cc" } } ], "extra": [ 1, 116, 70, 187, 96, 180, 222, 37, 13, 126, 232, 249, 57, 172, 194, 60, 141, 45, 91, 150, 63, 60, 252, 63, 19, 84, 221, 39, 73, 236, 77, 143, 247, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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