Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22c0be742f18b35563befe12ac6f5c596a419697f58ad1bca6e44d701a803944

Tx prefix hash: 2c993cb0a3c228c4a6867c969b837017160ac7572a9536bc0f088d40bfff31fb
Tx public key: e57110cb4fb56dd04ff0ec93ca12c6ef2b4a54b324c863b79e51c63c6db06fa9
Timestamp: 1763507755 Timestamp [UCT]: 2025-11-18 23:15:55 Age [y:d:h:m:s]: 00:009:06:37:00
Block: 1415126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6645 RingCT/type: yes/0
Extra: 01e57110cb4fb56dd04ff0ec93ca12c6ef2b4a54b324c863b79e51c63c6db06fa90211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c41962ecc24fc5272a0f0da8f7c39b321be313dc418dcbb6a24a00b95d5943bf 0.600000000000 1903621 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": 1415136, "vin": [ { "gen": { "height": 1415126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c41962ecc24fc5272a0f0da8f7c39b321be313dc418dcbb6a24a00b95d5943bf" } } ], "extra": [ 1, 229, 113, 16, 203, 79, 181, 109, 208, 79, 240, 236, 147, 202, 18, 198, 239, 43, 74, 84, 179, 36, 200, 99, 183, 158, 81, 198, 60, 109, 176, 111, 169, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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