Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f472f5a362f31bf37cc1feb56259d6f14b6df8953765e588c2c42dbded52154

Tx prefix hash: 45f467e2eaca35599c5052d504f97a8645f554e9adaca9d0e6408da98a510ed1
Tx public key: 26a98d8e4ae35faf060b063bb4961ff88ed0eabe57e5badb3f1f16a24c132580
Timestamp: 1752717129 Timestamp [UCT]: 2025-07-17 01:52:09 Age [y:d:h:m:s]: 00:095:03:36:50
Block: 1327095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66756 RingCT/type: yes/0
Extra: 0126a98d8e4ae35faf060b063bb4961ff88ed0eabe57e5badb3f1f16a24c132580021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd344045ee89867d782d437b10d4cbc75684caa8cbc5cb9bdc9a3b9b79901a5a 0.600000000000 1814848 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": 1327105, "vin": [ { "gen": { "height": 1327095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd344045ee89867d782d437b10d4cbc75684caa8cbc5cb9bdc9a3b9b79901a5a" } } ], "extra": [ 1, 38, 169, 141, 142, 74, 227, 95, 175, 6, 11, 6, 59, 180, 150, 31, 248, 142, 208, 234, 190, 87, 229, 186, 219, 63, 31, 22, 162, 76, 19, 37, 128, 2, 17, 0, 0, 0, 1, 228, 220, 144, 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