Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72b779d7b107ad36a33793363c2b9dd0242b46e7f8c93ad85f50c945e2e51256

Tx prefix hash: 52f18e83b33d74707633b6a9eead47b54c3dde2066564f0c4da86c463eff1c46
Tx public key: 314985f4ab0e5457c1df83a276eb71b8a141a0d8787edd8527102c7d9fbfc818
Timestamp: 1766077430 Timestamp [UCT]: 2025-12-18 17:03:50 Age [y:d:h:m:s]: 00:045:20:49:00
Block: 1436422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32668 RingCT/type: yes/0
Extra: 01314985f4ab0e5457c1df83a276eb71b8a141a0d8787edd8527102c7d9fbfc8180211000000067b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aaaabd6dfa4769c281d58bd4a0056b26918e68fef4da36c30c54576c61e9ae51 0.600000000000 1925227 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": 1436432, "vin": [ { "gen": { "height": 1436422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aaaabd6dfa4769c281d58bd4a0056b26918e68fef4da36c30c54576c61e9ae51" } } ], "extra": [ 1, 49, 73, 133, 244, 171, 14, 84, 87, 193, 223, 131, 162, 118, 235, 113, 184, 161, 65, 160, 216, 120, 126, 221, 133, 39, 16, 44, 125, 159, 191, 200, 24, 2, 17, 0, 0, 0, 6, 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