Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8dacdfed7776bb4e372cd059beec42db788632fb82d748e49117ae84ed13221

Tx prefix hash: 4a9a7aa08b68336bfc935f28d26531fcf3091212f13a1ecfb9c7362b5c86227e
Tx public key: f64f950c17ad49946047f9b90809f41a7b0d932ff53b7b4f9095fd65060635f8
Timestamp: 1752775739 Timestamp [UCT]: 2025-07-17 18:08:59 Age [y:d:h:m:s]: 00:170:22:24:57
Block: 1327578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121019 RingCT/type: yes/0
Extra: 01f64f950c17ad49946047f9b90809f41a7b0d932ff53b7b4f9095fd65060635f80211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 344f81c4ef616908c166f016a8fd562765c85b6515e4426e1dac96e604999ca2 0.600000000000 1815335 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": 1327588, "vin": [ { "gen": { "height": 1327578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "344f81c4ef616908c166f016a8fd562765c85b6515e4426e1dac96e604999ca2" } } ], "extra": [ 1, 246, 79, 149, 12, 23, 173, 73, 148, 96, 71, 249, 185, 8, 9, 244, 26, 123, 13, 147, 47, 245, 59, 123, 79, 144, 149, 253, 101, 6, 6, 53, 248, 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