Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cf37bb9f46cae1ca663a3db317f369b4c4abcb709c4f0123c3c0a05719a9d85

Tx prefix hash: 05fee5ee861200767c834bcf7fd0b5c956868c964b60309888e99bd2b99ec417
Tx public key: e6ddfaae0727950d8c8b37e52bda1820dbb6a661931678c1627f95c00d41ccb2
Timestamp: 1764626117 Timestamp [UCT]: 2025-12-01 21:55:17 Age [y:d:h:m:s]: 00:059:08:33:30
Block: 1424399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42321 RingCT/type: yes/0
Extra: 01e6ddfaae0727950d8c8b37e52bda1820dbb6a661931678c1627f95c00d41ccb20211000000028ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dacff87e4b9bf31b44da8f2a47435df45986e9d057abd4a7f6e66b2952387321 0.600000000000 1913030 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": 1424409, "vin": [ { "gen": { "height": 1424399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dacff87e4b9bf31b44da8f2a47435df45986e9d057abd4a7f6e66b2952387321" } } ], "extra": [ 1, 230, 221, 250, 174, 7, 39, 149, 13, 140, 139, 55, 229, 43, 218, 24, 32, 219, 182, 166, 97, 147, 22, 120, 193, 98, 127, 149, 192, 13, 65, 204, 178, 2, 17, 0, 0, 0, 2, 140, 235, 127, 9, 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