Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ce6ed967f04214c3b6f1316420ff7e5ed821503b7392b2aa37b1c4197a6d88a

Tx prefix hash: 33b5ca5d56f0001c50471383ec214ae60771cb99f5b59837b6167b7a9f5710b5
Tx public key: aa529454603724214a012fa12c86dd09ffceecaba5d9d76e045903121a106a6c
Timestamp: 1699366258 Timestamp [UCT]: 2023-11-07 14:10:58 Age [y:d:h:m:s]: 01:046:13:28:14
Block: 886491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294714 RingCT/type: yes/0
Extra: 01aa529454603724214a012fa12c86dd09ffceecaba5d9d76e045903121a106a6c02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.709067076000 dcy

stealth address amount amount idx
00: f1edbf3e10d6e6d7e48a10480ec823d31674537d764065f4935328349422a8a9 0.709067076000 1342318 of 0

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": 886501, "vin": [ { "gen": { "height": 886491 } } ], "vout": [ { "amount": 709067076, "target": { "key": "f1edbf3e10d6e6d7e48a10480ec823d31674537d764065f4935328349422a8a9" } } ], "extra": [ 1, 170, 82, 148, 84, 96, 55, 36, 33, 74, 1, 47, 161, 44, 134, 221, 9, 255, 206, 236, 171, 165, 217, 215, 110, 4, 89, 3, 18, 26, 16, 106, 108, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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