Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f696df2b91e8f26a96628c2a8d1cb5f459f96c308254a26cdf85b59a8cc9e7a

Tx prefix hash: 991749a00967c671c45afb3404b5b2d8370496321bef2fac26a007bb565bf1f3
Tx public key: 697ec21e505196d766d1d703d0597f8156b12a1320d3141bbbdc67346d5b3f81
Timestamp: 1751512697 Timestamp [UCT]: 2025-07-03 03:18:17 Age [y:d:h:m:s]: 00:185:07:28:37
Block: 1317658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130770 RingCT/type: yes/0
Extra: 01697ec21e505196d766d1d703d0597f8156b12a1320d3141bbbdc67346d5b3f81021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d734bb1ab43d527a3b3938e8ab1425614a7a6b4ca8a5c0fdf4bfb30a433fd06 0.600000000000 1805327 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": 1317668, "vin": [ { "gen": { "height": 1317658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d734bb1ab43d527a3b3938e8ab1425614a7a6b4ca8a5c0fdf4bfb30a433fd06" } } ], "extra": [ 1, 105, 126, 194, 30, 80, 81, 150, 215, 102, 209, 215, 3, 208, 89, 127, 129, 86, 177, 42, 19, 32, 211, 20, 27, 187, 220, 103, 52, 109, 91, 63, 129, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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