Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfb8a7e5cd277ac333eb2f7281c5afc2f17179474d84e36572a596432b8f4835

Tx prefix hash: c9f0f4e04ce49709048f0d936a9e629c58f499c72209bc7de2e342d9980b610a
Tx public key: 4a4039d67967cfc741ab50ce1a3c6cc2e66ae6a21450cc04e639e2b794f91c18
Timestamp: 1761705202 Timestamp [UCT]: 2025-10-29 02:33:22 Age [y:d:h:m:s]: 00:070:11:09:22
Block: 1400205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50444 RingCT/type: yes/0
Extra: 014a4039d67967cfc741ab50ce1a3c6cc2e66ae6a21450cc04e639e2b794f91c1802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a19f4f77a381e24ea7d271374d30bcb35bce79913ba966a13f95f4d564587d31 0.600000000000 1888512 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": 1400215, "vin": [ { "gen": { "height": 1400205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a19f4f77a381e24ea7d271374d30bcb35bce79913ba966a13f95f4d564587d31" } } ], "extra": [ 1, 74, 64, 57, 214, 121, 103, 207, 199, 65, 171, 80, 206, 26, 60, 108, 194, 230, 106, 230, 162, 20, 80, 204, 4, 230, 57, 226, 183, 148, 249, 28, 24, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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