Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73528b1bea9745ed3c5a9739736ab73baf627be0a936865424aabb3251570881

Tx prefix hash: 484a8a6a0ea1ac73ea91b719d1e4b0014bd245b13759e71e724ec2883d524276
Tx public key: d6d8f3b9de1526a0bab3dfeef5f046c3d75b9f8ede92d4fd551372c266cbfd51
Timestamp: 1763950234 Timestamp [UCT]: 2025-11-24 02:10:34 Age [y:d:h:m:s]: 00:029:21:55:55
Block: 1418793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21407 RingCT/type: yes/0
Extra: 01d6d8f3b9de1526a0bab3dfeef5f046c3d75b9f8ede92d4fd551372c266cbfd5102110000000ed6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9dfe1c56d82f6e345253d2f5e57fac419da6b713d19dcc00d8999ed6778e8bf0 0.600000000000 1907326 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": 1418803, "vin": [ { "gen": { "height": 1418793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dfe1c56d82f6e345253d2f5e57fac419da6b713d19dcc00d8999ed6778e8bf0" } } ], "extra": [ 1, 214, 216, 243, 185, 222, 21, 38, 160, 186, 179, 223, 238, 245, 240, 70, 195, 215, 91, 159, 142, 222, 146, 212, 253, 85, 19, 114, 194, 102, 203, 253, 81, 2, 17, 0, 0, 0, 14, 214, 225, 157, 124, 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