Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09013adfd1912e2d3b628046df0840b8bf8eccb40d2e96239b2b3adf8c49bb7d

Tx prefix hash: fb223d12591c3cdb8fd2819a94596d5ae3e54ff5a7d3521b5b61ebe62c33bc31
Tx public key: 1e239b77e1722577de5350ed26ef3bdcf6dd8f189fffbdfec5d174a97a32908d
Timestamp: 1751978117 Timestamp [UCT]: 2025-07-08 12:35:17 Age [y:d:h:m:s]: 00:176:04:10:57
Block: 1321311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124413 RingCT/type: yes/0
Extra: 011e239b77e1722577de5350ed26ef3bdcf6dd8f189fffbdfec5d174a97a32908d021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e61613069553d1d5e50a8a3db1f160e7f78ac7460292d4dfdd43c191a12715bf 0.600000000000 1809016 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": 1321321, "vin": [ { "gen": { "height": 1321311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e61613069553d1d5e50a8a3db1f160e7f78ac7460292d4dfdd43c191a12715bf" } } ], "extra": [ 1, 30, 35, 155, 119, 225, 114, 37, 119, 222, 83, 80, 237, 38, 239, 59, 220, 246, 221, 143, 24, 159, 255, 189, 254, 197, 209, 116, 169, 122, 50, 144, 141, 2, 17, 0, 0, 0, 2, 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