Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 535ffa375374944e0e73a93c7d510699ac5ca3cafad96243ede6e92b8fd75385

Tx prefix hash: d5f3e0d1f0056981ecd67681e5f710447afbabad1ff576bf2d3e252d96d0c104
Tx public key: d0a3ffa78b550cd1e00e295a02d4d6ed1fd704e405d2574bed2e8bbdc9cf1776
Timestamp: 1747501232 Timestamp [UCT]: 2025-05-17 17:00:32 Age [y:d:h:m:s]: 00:143:09:48:12
Block: 1285013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100137 RingCT/type: yes/0
Extra: 01d0a3ffa78b550cd1e00e295a02d4d6ed1fd704e405d2574bed2e8bbdc9cf17760211000000069f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37d45af6d4cf24f5315a4701be024231cf8a668175970d372b8538b1b55bfbb5 0.600000000000 1772476 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": 1285023, "vin": [ { "gen": { "height": 1285013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37d45af6d4cf24f5315a4701be024231cf8a668175970d372b8538b1b55bfbb5" } } ], "extra": [ 1, 208, 163, 255, 167, 139, 85, 12, 209, 224, 14, 41, 90, 2, 212, 214, 237, 31, 215, 4, 228, 5, 210, 87, 75, 237, 46, 139, 189, 201, 207, 23, 118, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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