Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6edbb6ed8dfea1d9ba7470b58777184d299335fa5e4e304f35d73081965c606

Tx prefix hash: 4f1f82b66fe6cac24e1e10de4a17216aaf5e6855790b9980b5b5391f76c81b87
Tx public key: 953294fb91522d9efb23e162667012647f44c0ec239df4ac1f78a26cc0620290
Timestamp: 1706580049 Timestamp [UCT]: 2024-01-30 02:00:49 Age [y:d:h:m:s]: 01:093:16:45:57
Block: 946275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328065 RingCT/type: yes/0
Extra: 01953294fb91522d9efb23e162667012647f44c0ec239df4ac1f78a26cc06202900211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68ea609ea3c04d5563d42f0e30cfee25f91e0d5e3198e47824470a09a5d2c246 0.600000000000 1404607 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": 946285, "vin": [ { "gen": { "height": 946275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68ea609ea3c04d5563d42f0e30cfee25f91e0d5e3198e47824470a09a5d2c246" } } ], "extra": [ 1, 149, 50, 148, 251, 145, 82, 45, 158, 251, 35, 225, 98, 102, 112, 18, 100, 127, 68, 192, 236, 35, 157, 244, 172, 31, 120, 162, 108, 192, 98, 2, 144, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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