Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 322bf564c2e03fbd60ecb46be37e00774f35418ece17d2b8d01afe0105bb3bf1

Tx prefix hash: 5617b610f4c2c845ca5f5d80b9d3d85839881d679efad75f7904873f0bdb9127
Tx public key: 9a5040faedf04134fdabe9b947e190baae5d615696d8d550b2094d7d159d0d51
Timestamp: 1749732704 Timestamp [UCT]: 2025-06-12 12:51:44 Age [y:d:h:m:s]: 00:151:08:42:38
Block: 1303465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105886 RingCT/type: yes/0
Extra: 019a5040faedf04134fdabe9b947e190baae5d615696d8d550b2094d7d159d0d51021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46edd5f78d5a615e883d99f522cceccfc76c7a0497d9793b57fb87ce8ed69ea9 0.600000000000 1791046 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": 1303475, "vin": [ { "gen": { "height": 1303465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46edd5f78d5a615e883d99f522cceccfc76c7a0497d9793b57fb87ce8ed69ea9" } } ], "extra": [ 1, 154, 80, 64, 250, 237, 240, 65, 52, 253, 171, 233, 185, 71, 225, 144, 186, 174, 93, 97, 86, 150, 216, 213, 80, 178, 9, 77, 125, 21, 157, 13, 81, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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