Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34cff92b1dc5508db70f513fc9af0b0f3c47f40e1f95ee748ede6b7afa02ba3f

Tx prefix hash: e463e5ec6a17547ffba014b9083091790d0d9c734de0fb01c2bb7c8c781c6bcb
Tx public key: 7bb5920a349ceebda21082058a05a662a45065bc3350f97dc8209d13c3b97c2f
Timestamp: 1736837837 Timestamp [UCT]: 2025-01-14 06:57:17 Age [y:d:h:m:s]: 00:156:12:02:45
Block: 1197000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111552 RingCT/type: yes/0
Extra: 017bb5920a349ceebda21082058a05a662a45065bc3350f97dc8209d13c3b97c2f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62252a3dfef49e60fd4fdd7aa53af97e1d75ce160fb800236ec65b0d2e912b55 0.600000000000 1683605 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": 1197010, "vin": [ { "gen": { "height": 1197000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62252a3dfef49e60fd4fdd7aa53af97e1d75ce160fb800236ec65b0d2e912b55" } } ], "extra": [ 1, 123, 181, 146, 10, 52, 156, 238, 189, 162, 16, 130, 5, 138, 5, 166, 98, 164, 80, 101, 188, 51, 80, 249, 125, 200, 32, 157, 19, 195, 185, 124, 47, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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