Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 697f485670533a790f09ed3448d183a10dedf44e45fb11e7927c7d5a50466229

Tx prefix hash: 3dd27d7a5b72072651a41fe335de15556a7fe7dd5b3e2c4b5bc77b2b33153c4d
Tx public key: aefa1927d853e05821c42ed2d9b1df277a06ecba4031e6800eb5b216d438342c
Timestamp: 1736145556 Timestamp [UCT]: 2025-01-06 06:39:16 Age [y:d:h:m:s]: 00:163:12:06:37
Block: 1191293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116534 RingCT/type: yes/0
Extra: 01aefa1927d853e05821c42ed2d9b1df277a06ecba4031e6800eb5b216d438342c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05a02e296499dd766d7841ea451bbde8644fd0b4d1f24a76d255af3983c6b6ff 0.600000000000 1677818 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": 1191303, "vin": [ { "gen": { "height": 1191293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05a02e296499dd766d7841ea451bbde8644fd0b4d1f24a76d255af3983c6b6ff" } } ], "extra": [ 1, 174, 250, 25, 39, 216, 83, 224, 88, 33, 196, 46, 210, 217, 177, 223, 39, 122, 6, 236, 186, 64, 49, 230, 128, 14, 181, 178, 22, 212, 56, 52, 44, 2, 17, 0, 0, 0, 2, 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