Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c67b4417b71d7093b309e220095170d06352ee4195fd612ffe9551d0cf72e866

Tx prefix hash: 24779270e4dc626c3d0c59da2f09ec2b930139527c43abf2c077920be8a4597c
Tx public key: 33cef26f07c3f73afe92d5faba5b194812b562aefcfb2fa23c8c9184d0a938e3
Timestamp: 1728601552 Timestamp [UCT]: 2024-10-10 23:05:52 Age [y:d:h:m:s]: 00:218:06:10:44
Block: 1128871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155793 RingCT/type: yes/0
Extra: 0133cef26f07c3f73afe92d5faba5b194812b562aefcfb2fa23c8c9184d0a938e302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05a7214f0dba0d7d464072c170d38b94e76d04901540a9b23406bd0f540846ce 0.600000000000 1611694 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": 1128881, "vin": [ { "gen": { "height": 1128871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05a7214f0dba0d7d464072c170d38b94e76d04901540a9b23406bd0f540846ce" } } ], "extra": [ 1, 51, 206, 242, 111, 7, 195, 247, 58, 254, 146, 213, 250, 186, 91, 25, 72, 18, 181, 98, 174, 252, 251, 47, 162, 60, 140, 145, 132, 208, 169, 56, 227, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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