Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79964bd07919b22621a9f476b3591b120ad7c0c969ea9259f53e54f8155c250e

Tx prefix hash: 516fa3d58187830cbc0b3138ef8f393536cf9df052b7790029b839887cc3a041
Tx public key: 427df1b979d047c320f5e0654d2ec1487155f40b97e4e56455b7e821ff76e60b
Timestamp: 1749475875 Timestamp [UCT]: 2025-06-09 13:31:15 Age [y:d:h:m:s]: 00:161:07:56:54
Block: 1301373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112986 RingCT/type: yes/0
Extra: 01427df1b979d047c320f5e0654d2ec1487155f40b97e4e56455b7e821ff76e60b021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6dc3ba7f1ee17e20ee161e3eb5aeb318bf64f01adfbc9476cd2f27f68210ff5 0.600000000000 1788930 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": 1301383, "vin": [ { "gen": { "height": 1301373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6dc3ba7f1ee17e20ee161e3eb5aeb318bf64f01adfbc9476cd2f27f68210ff5" } } ], "extra": [ 1, 66, 125, 241, 185, 121, 208, 71, 195, 32, 245, 224, 101, 77, 46, 193, 72, 113, 85, 244, 11, 151, 228, 229, 100, 85, 183, 232, 33, 255, 118, 230, 11, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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