Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 730f294b1c88f148af75b8d12a16da2a50cbd4e0e194f1864f513573a46fadfa

Tx prefix hash: 680b8826b31a8a11521c23f44e60895a5e668cda54f99f80bbef12d79f0e1f41
Tx public key: 8aaaed6e1f40b7f19e08ad95f05169fd8e9f609a9fed7184eab540bd14813d03
Timestamp: 1712299246 Timestamp [UCT]: 2024-04-05 06:40:46 Age [y:d:h:m:s]: 00:224:04:54:58
Block: 993685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160531 RingCT/type: yes/0
Extra: 018aaaed6e1f40b7f19e08ad95f05169fd8e9f609a9fed7184eab540bd14813d0302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 424bebe8f344bc5bc51a0d15a50ab93adf94732946b225f992f5167b76ddf24d 0.600000000000 1454073 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": 993695, "vin": [ { "gen": { "height": 993685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "424bebe8f344bc5bc51a0d15a50ab93adf94732946b225f992f5167b76ddf24d" } } ], "extra": [ 1, 138, 170, 237, 110, 31, 64, 183, 241, 158, 8, 173, 149, 240, 81, 105, 253, 142, 159, 96, 154, 159, 237, 113, 132, 234, 181, 64, 189, 20, 129, 61, 3, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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