Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d98bbd16e413402848061ad015e6be7a544de5bed063a6af902fd05c0cfa3a17

Tx prefix hash: dd9b382214033d7bebde51d2267c28e2b59394776d390fcb0062673a2e0ae5a5
Tx public key: 7c42ca2985877cbf14d2c21d031ff7204feb2dec30e5eef26b84bcce8d0c7aed
Timestamp: 1732510320 Timestamp [UCT]: 2024-11-25 04:52:00 Age [y:d:h:m:s]: 01:066:00:33:13
Block: 1161165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305521 RingCT/type: yes/0
Extra: 017c42ca2985877cbf14d2c21d031ff7204feb2dec30e5eef26b84bcce8d0c7aed0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f290a46081e67e66e5ca11fe9cb9b2098b44379d4421a7e9f2c547675744a1d 0.600000000000 1646816 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": 1161175, "vin": [ { "gen": { "height": 1161165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f290a46081e67e66e5ca11fe9cb9b2098b44379d4421a7e9f2c547675744a1d" } } ], "extra": [ 1, 124, 66, 202, 41, 133, 135, 124, 191, 20, 210, 194, 29, 3, 31, 247, 32, 79, 235, 45, 236, 48, 229, 238, 242, 107, 132, 188, 206, 141, 12, 122, 237, 2, 17, 0, 0, 0, 4, 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