Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc1caffda6111c13b5d2f57178259fbd0fccea06919f1e1104759e105c05d7fa

Tx prefix hash: 2f4954588f92bf1cd86c3a50b7ecd8daf70ab3132504dd887b3b7d7e65ba7bcd
Tx public key: 2a95650d3e82dc6ae0900508d05f8e19c174b2a1b9de97506d15098db7195079
Timestamp: 1714458194 Timestamp [UCT]: 2024-04-30 06:23:14 Age [y:d:h:m:s]: 01:191:03:41:09
Block: 1011607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395254 RingCT/type: yes/0
Extra: 012a95650d3e82dc6ae0900508d05f8e19c174b2a1b9de97506d15098db71950790211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e315e08490b07629c6a54e92113a8354c77236c716a8db9f0816c1abcd416ec 0.600000000000 1473879 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": 1011617, "vin": [ { "gen": { "height": 1011607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e315e08490b07629c6a54e92113a8354c77236c716a8db9f0816c1abcd416ec" } } ], "extra": [ 1, 42, 149, 101, 13, 62, 130, 220, 106, 224, 144, 5, 8, 208, 95, 142, 25, 193, 116, 178, 161, 185, 222, 151, 80, 109, 21, 9, 141, 183, 25, 80, 121, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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