Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05013919dc8e3d77f7f97c709760d2087494800065214fe50006a46c8bd4911d

Tx prefix hash: 6449b0b84411c7cb30c15c176ac562c86eac4408f0c0fe3fb4da16eece3e8bec
Tx public key: d5cbf21325eba971cecb9014cce0bbb3278a19d424f9a1b63fb34e2aa9006d32
Timestamp: 1750238301 Timestamp [UCT]: 2025-06-18 09:18:21 Age [y:d:h:m:s]: 00:153:17:37:42
Block: 1307558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107679 RingCT/type: yes/0
Extra: 01d5cbf21325eba971cecb9014cce0bbb3278a19d424f9a1b63fb34e2aa9006d32021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13a5b26d0fdae25679c2296df4eabc5eabb6e524986bb47fc98755b18cd7bbca 0.600000000000 1795169 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": 1307568, "vin": [ { "gen": { "height": 1307558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13a5b26d0fdae25679c2296df4eabc5eabb6e524986bb47fc98755b18cd7bbca" } } ], "extra": [ 1, 213, 203, 242, 19, 37, 235, 169, 113, 206, 203, 144, 20, 204, 224, 187, 179, 39, 138, 25, 212, 36, 249, 161, 182, 63, 179, 78, 42, 169, 0, 109, 50, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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