Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ba410f8e077c640d49d77c505789f71aa75cfee59a54dd767ab5b7679746ea3

Tx prefix hash: bd723ce5bea464bdedf201682a2286518999f2225b193406f4566e3720fb2274
Tx public key: d5d70125e971ea5dca077934e6b24cde8d2997372cf42f900efe2580992d3c5b
Timestamp: 1764368690 Timestamp [UCT]: 2025-11-28 22:24:50 Age [y:d:h:m:s]: 00:038:23:21:06
Block: 1422267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27904 RingCT/type: yes/0
Extra: 01d5d70125e971ea5dca077934e6b24cde8d2997372cf42f900efe2580992d3c5b021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ae11b7633667b4bc7d4f0d1e0868db9a75b4448e94ea465d5434ac361d1d6ee 0.600000000000 1910832 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": 1422277, "vin": [ { "gen": { "height": 1422267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ae11b7633667b4bc7d4f0d1e0868db9a75b4448e94ea465d5434ac361d1d6ee" } } ], "extra": [ 1, 213, 215, 1, 37, 233, 113, 234, 93, 202, 7, 121, 52, 230, 178, 76, 222, 141, 41, 151, 55, 44, 244, 47, 144, 14, 254, 37, 128, 153, 45, 60, 91, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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