Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01afe69a61c591fa82734c280def63d08f2ab33a60bcded182140481a56f4b42

Tx prefix hash: a6840ff4ad1fb79b1bdd8207a7a1546b51c1fe33f6f4940eeec324baf7f49621
Tx public key: af3a7aaf4aa54e8d288c78df4306d12c392dbec22c18eb466e8216aabcfa846b
Timestamp: 1738242347 Timestamp [UCT]: 2025-01-30 13:05:47 Age [y:d:h:m:s]: 00:139:01:17:01
Block: 1208368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99331 RingCT/type: yes/0
Extra: 01af3a7aaf4aa54e8d288c78df4306d12c392dbec22c18eb466e8216aabcfa846b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9e4a14c04508b21eb81840a8826b1b4b66b1ac6ae8a63adf187f111022cf519 0.600000000000 1695099 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": 1208378, "vin": [ { "gen": { "height": 1208368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9e4a14c04508b21eb81840a8826b1b4b66b1ac6ae8a63adf187f111022cf519" } } ], "extra": [ 1, 175, 58, 122, 175, 74, 165, 78, 141, 40, 140, 120, 223, 67, 6, 209, 44, 57, 45, 190, 194, 44, 24, 235, 70, 110, 130, 22, 170, 188, 250, 132, 107, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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