Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc95a56002415bdd1aea3d691e20383e1b258fd5d328967e1ff57c9c340dc9ff

Tx prefix hash: 78afeab0da8edd88b6b42cb9873879ef6ac81d47e019129f2d72a8c46b484f3c
Tx public key: 2beb4450e9b94327718b9eba339596cf98ace2b2027a8cb755618b8a6371bdaa
Timestamp: 1754196528 Timestamp [UCT]: 2025-08-03 04:48:48 Age [y:d:h:m:s]: 00:117:01:08:25
Block: 1339185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82590 RingCT/type: yes/0
Extra: 012beb4450e9b94327718b9eba339596cf98ace2b2027a8cb755618b8a6371bdaa021100000005ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e045787fc4f0c1b150b6b125c38799c5502139426e2e865f2adf01ccb850320 0.600000000000 1826998 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": 1339195, "vin": [ { "gen": { "height": 1339185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e045787fc4f0c1b150b6b125c38799c5502139426e2e865f2adf01ccb850320" } } ], "extra": [ 1, 43, 235, 68, 80, 233, 185, 67, 39, 113, 139, 158, 186, 51, 149, 150, 207, 152, 172, 226, 178, 2, 122, 140, 183, 85, 97, 139, 138, 99, 113, 189, 170, 2, 17, 0, 0, 0, 5, 173, 121, 72, 208, 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