Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a81a65783220344bd60e5a5acecc220d172c4ce6116a69d690478b6e8ea03afc

Tx prefix hash: d0a4dcd6af19e0682a1603d994886a9a8da128afd47d1ba6e56905f95b307bea
Tx public key: b924fa2015ceb385f6a77bd48e90c2d78477ce1314ca76ff958dc1f4a2c7f386
Timestamp: 1750465318 Timestamp [UCT]: 2025-06-21 00:21:58 Age [y:d:h:m:s]: 00:146:10:24:24
Block: 1309399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102494 RingCT/type: yes/0
Extra: 01b924fa2015ceb385f6a77bd48e90c2d78477ce1314ca76ff958dc1f4a2c7f386021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd021b454a53092866b29a93519fcbbc9f5b169a2a1d72d1f8a97e7e700f9cc8 0.600000000000 1797014 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": 1309409, "vin": [ { "gen": { "height": 1309399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd021b454a53092866b29a93519fcbbc9f5b169a2a1d72d1f8a97e7e700f9cc8" } } ], "extra": [ 1, 185, 36, 250, 32, 21, 206, 179, 133, 246, 167, 123, 212, 142, 144, 194, 215, 132, 119, 206, 19, 20, 202, 118, 255, 149, 141, 193, 244, 162, 199, 243, 134, 2, 17, 0, 0, 0, 1, 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