Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45a74f58205a6829aee9852357f231db7148fcbc7b49b9176f34dec0a06b083f

Tx prefix hash: c33eb3b166570436f25fa5adad99a078d5f6fbd6dde30c32e9b047d8d8f8b5b6
Tx public key: e72edd2c8b36dd8349eb596aa7d0480a41fdb65d350b2c1462a24fb60db311e9
Timestamp: 1766142907 Timestamp [UCT]: 2025-12-19 11:15:07 Age [y:d:h:m:s]: 00:016:04:59:01
Block: 1436969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11621 RingCT/type: yes/0
Extra: 01e72edd2c8b36dd8349eb596aa7d0480a41fdb65d350b2c1462a24fb60db311e90211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cba87caad3bf957269e942351d75a21284814392d3cf06fb8877205e79d6a87 0.600000000000 1925774 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": 1436979, "vin": [ { "gen": { "height": 1436969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cba87caad3bf957269e942351d75a21284814392d3cf06fb8877205e79d6a87" } } ], "extra": [ 1, 231, 46, 221, 44, 139, 54, 221, 131, 73, 235, 89, 106, 167, 208, 72, 10, 65, 253, 182, 93, 53, 11, 44, 20, 98, 162, 79, 182, 13, 179, 17, 233, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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