Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd930e09a0e0d21aebdf93dca32b7edbe814e46511319e0742cc1b04d1f6d843

Tx prefix hash: f2cbe83c0e47c28e25ac8a5a2b15e440cf25adbd2adf1578ab09bfab10263bf5
Tx public key: 6f97c43225f6633d444e3bb914c5ad0050f7c592794d36cf25d04c4a9dcab20c
Timestamp: 1764346322 Timestamp [UCT]: 2025-11-28 16:12:02 Age [y:d:h:m:s]: 00:035:20:40:52
Block: 1422083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25676 RingCT/type: yes/0
Extra: 016f97c43225f6633d444e3bb914c5ad0050f7c592794d36cf25d04c4a9dcab20c021100000001da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46644d4c9c457d654c4bdc4270f76d70ae482390ca4844ce3c925b3bba80fbfc 0.600000000000 1910648 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": 1422093, "vin": [ { "gen": { "height": 1422083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46644d4c9c457d654c4bdc4270f76d70ae482390ca4844ce3c925b3bba80fbfc" } } ], "extra": [ 1, 111, 151, 196, 50, 37, 246, 99, 61, 68, 78, 59, 185, 20, 197, 173, 0, 80, 247, 197, 146, 121, 77, 54, 207, 37, 208, 76, 74, 157, 202, 178, 12, 2, 17, 0, 0, 0, 1, 218, 85, 72, 72, 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