Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9e2a2f02e5c9182cd4ab75ccfa09252db0b9eedf2d5c9b3dca2a3f0d48435ee

Tx prefix hash: d0b709f82c18ff2391264701979741b399d82f85bfc7c901bc2b58fbe9e5ba4a
Tx public key: e2663be2ca46d7421016d68e7d634c11659c25a2656ce0e903d34a5159577c30
Timestamp: 1734259511 Timestamp [UCT]: 2024-12-15 10:45:11 Age [y:d:h:m:s]: 00:120:19:54:24
Block: 1175687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86127 RingCT/type: yes/0
Extra: 01e2663be2ca46d7421016d68e7d634c11659c25a2656ce0e903d34a5159577c300211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a253e0d06a9d6ab2997b0ccd64cf89b70ad69325b157fcf5ba7418e3274ed2e 0.600000000000 1662002 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": 1175697, "vin": [ { "gen": { "height": 1175687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a253e0d06a9d6ab2997b0ccd64cf89b70ad69325b157fcf5ba7418e3274ed2e" } } ], "extra": [ 1, 226, 102, 59, 226, 202, 70, 215, 66, 16, 22, 214, 142, 125, 99, 76, 17, 101, 156, 37, 162, 101, 108, 224, 233, 3, 211, 74, 81, 89, 87, 124, 48, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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