Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c42241b09594f456ecb107e83d7a55347d526a0f15bbb326f539c1f63f61b55f

Tx prefix hash: 5c70448f9ff276b8f8abab1eb73948666127e06473118136ee7dc17a9a394b57
Tx public key: 00a083b22dc0381538fb3528d876ed43e5ec35f1a0de46b8a494b56e87ae862d
Timestamp: 1762005410 Timestamp [UCT]: 2025-11-01 13:56:50 Age [y:d:h:m:s]: 00:005:08:19:49
Block: 1402706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3799 RingCT/type: yes/0
Extra: 0100a083b22dc0381538fb3528d876ed43e5ec35f1a0de46b8a494b56e87ae862d021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 204b9f934d7514a1af47f346ef69d8019c02b80482092fb001afcd1337e19acb 0.600000000000 1891025 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": 1402716, "vin": [ { "gen": { "height": 1402706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "204b9f934d7514a1af47f346ef69d8019c02b80482092fb001afcd1337e19acb" } } ], "extra": [ 1, 0, 160, 131, 178, 45, 192, 56, 21, 56, 251, 53, 40, 216, 118, 237, 67, 229, 236, 53, 241, 160, 222, 70, 184, 164, 148, 181, 110, 135, 174, 134, 45, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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