Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa2ea4df8db00e85d4e0683fbd56ddf705a7908e08d796ccf9660586e1551075

Tx prefix hash: 74f1ba10e60a36edfd600be114cc163c3e70073e9979b7b757c2646c1862b797
Tx public key: 28c3fb4c7e2a9d7f0b5e1e94e1b1f05aa0f8ba4f907cf7e1daae1c66ce2e9e16
Timestamp: 1756044320 Timestamp [UCT]: 2025-08-24 14:05:20 Age [y:d:h:m:s]: 00:089:00:03:34
Block: 1353464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63531 RingCT/type: yes/0
Extra: 0128c3fb4c7e2a9d7f0b5e1e94e1b1f05aa0f8ba4f907cf7e1daae1c66ce2e9e160211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83b18b75c9e909ade911a686f9f890c8305787cd90a00a9968755d88c6147161 0.600000000000 1841439 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": 1353474, "vin": [ { "gen": { "height": 1353464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83b18b75c9e909ade911a686f9f890c8305787cd90a00a9968755d88c6147161" } } ], "extra": [ 1, 40, 195, 251, 76, 126, 42, 157, 127, 11, 94, 30, 148, 225, 177, 240, 90, 160, 248, 186, 79, 144, 124, 247, 225, 218, 174, 28, 102, 206, 46, 158, 22, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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