Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c80a151f0c3b88caa82c567ebe7e7b3434e9eef453a3ee55429ff7357a1b65a

Tx prefix hash: e75e3e6b0b4c3369350d42be67867341ae3de9314a65d7ae82494f1bd7053db4
Tx public key: a415dedc5e62718a4aca13ce74d8eeb57a0e5fc16e676b9c80c872b8343b4244
Timestamp: 1760926702 Timestamp [UCT]: 2025-10-20 02:18:22 Age [y:d:h:m:s]: 00:080:10:43:24
Block: 1393757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57589 RingCT/type: yes/0
Extra: 01a415dedc5e62718a4aca13ce74d8eeb57a0e5fc16e676b9c80c872b8343b4244021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1114743bf2a7341d0d426fdc7055a41ec81743cef5493aa3bf891eb47d50026 0.600000000000 1882024 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": 1393767, "vin": [ { "gen": { "height": 1393757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1114743bf2a7341d0d426fdc7055a41ec81743cef5493aa3bf891eb47d50026" } } ], "extra": [ 1, 164, 21, 222, 220, 94, 98, 113, 138, 74, 202, 19, 206, 116, 216, 238, 181, 122, 14, 95, 193, 110, 103, 107, 156, 128, 200, 114, 184, 52, 59, 66, 68, 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