Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33c312e903b8d76cea41cd35b2402bab1c6892495e5ae55929bd2e9a4fee39d4

Tx prefix hash: 11857cadc92575a7c73d531b9a8bcc921e393171dab728973a70d07c08453c5c
Tx public key: e841d7c2e0d0ac7924ef443b68d09e904460b90ae8fa2342582af45dc7ed48cd
Timestamp: 1708567413 Timestamp [UCT]: 2024-02-22 02:03:33 Age [y:d:h:m:s]: 01:080:03:10:18
Block: 962773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318314 RingCT/type: yes/0
Extra: 01e841d7c2e0d0ac7924ef443b68d09e904460b90ae8fa2342582af45dc7ed48cd02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c66c5a08df1362f217b546749384455dd1cb8511cdb5e2b42d248d3f12602ab1 0.600000000000 1422456 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": 962783, "vin": [ { "gen": { "height": 962773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c66c5a08df1362f217b546749384455dd1cb8511cdb5e2b42d248d3f12602ab1" } } ], "extra": [ 1, 232, 65, 215, 194, 224, 208, 172, 121, 36, 239, 68, 59, 104, 208, 158, 144, 68, 96, 185, 10, 232, 250, 35, 66, 88, 42, 244, 93, 199, 237, 72, 205, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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