Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 306c63d2153f62bf1135a5d24c65b3034f282daaec55c24c6e578c9a53259823

Tx prefix hash: a1ac29e1557a6901116425e77aa840b6463a4aec816e8bb2fa36fa5a9b0d7095
Tx public key: 59516d01d35c17806dcd8d73eccb72c79bcca4a55ab5c8223baadcfb44523222
Timestamp: 1712902921 Timestamp [UCT]: 2024-04-12 06:22:01 Age [y:d:h:m:s]: 01:032:16:16:05
Block: 998690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284358 RingCT/type: yes/0
Extra: 0159516d01d35c17806dcd8d73eccb72c79bcca4a55ab5c8223baadcfb4452322202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 004a5e4eed97625f956a05d8d629940cb1f2f2370dc5b76e752a6288623086e9 0.600000000000 1459142 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": 998700, "vin": [ { "gen": { "height": 998690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "004a5e4eed97625f956a05d8d629940cb1f2f2370dc5b76e752a6288623086e9" } } ], "extra": [ 1, 89, 81, 109, 1, 211, 92, 23, 128, 109, 205, 141, 115, 236, 203, 114, 199, 155, 204, 164, 165, 90, 181, 200, 34, 59, 170, 220, 251, 68, 82, 50, 34, 2, 17, 0, 0, 0, 4, 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