Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73cae8f2e9cdd6616a63381057b538b8a5fc3a7051594d27d95bdb6664c458bb

Tx prefix hash: e078be302c74f2dccf629323032643829e83297f8fb8481ffae860622aad9f6d
Tx public key: 0ba823beb1c5b6394321adfc53a31613d3ef24162a978ff56dcd170f4e1bbcd9
Timestamp: 1751617858 Timestamp [UCT]: 2025-07-04 08:30:58 Age [y:d:h:m:s]: 00:136:21:50:12
Block: 1318496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96126 RingCT/type: yes/0
Extra: 010ba823beb1c5b6394321adfc53a31613d3ef24162a978ff56dcd170f4e1bbcd9021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a18ed74daf4c20b8be8083d07b5b47248d97efb4ab1d195bfc4217cf2a21553 0.600000000000 1806177 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": 1318506, "vin": [ { "gen": { "height": 1318496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a18ed74daf4c20b8be8083d07b5b47248d97efb4ab1d195bfc4217cf2a21553" } } ], "extra": [ 1, 11, 168, 35, 190, 177, 197, 182, 57, 67, 33, 173, 252, 83, 163, 22, 19, 211, 239, 36, 22, 42, 151, 143, 245, 109, 205, 23, 15, 78, 27, 188, 217, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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