Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24a1346e6ec94a6166776e99b5bba3b2251b41f8dfc84c3e81e5be7afa2a9359

Tx prefix hash: ca1b838087f9a1c8a53b420728f167a8ac7bab31cd89fe3617a8cdf54dbf1ee3
Tx public key: 4014428d3092ccd3c3639f108c4d3d7b24a56903f5d41fe27a3b9ca916e79a50
Timestamp: 1761451877 Timestamp [UCT]: 2025-10-26 04:11:17 Age [y:d:h:m:s]: 00:033:05:10:17
Block: 1398104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23773 RingCT/type: yes/0
Extra: 014014428d3092ccd3c3639f108c4d3d7b24a56903f5d41fe27a3b9ca916e79a500211000000035dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e862594a606bcdd8e2f8d6a883a986c9f73a30387b63b65c068052354b51260 0.600000000000 1886397 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": 1398114, "vin": [ { "gen": { "height": 1398104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e862594a606bcdd8e2f8d6a883a986c9f73a30387b63b65c068052354b51260" } } ], "extra": [ 1, 64, 20, 66, 141, 48, 146, 204, 211, 195, 99, 159, 16, 140, 77, 61, 123, 36, 165, 105, 3, 245, 212, 31, 226, 122, 59, 156, 169, 22, 231, 154, 80, 2, 17, 0, 0, 0, 3, 93, 251, 190, 42, 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