Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf4a84abe396dfd42f9e64998f4a4bd6a11b61aa4aaf0b4f9701bb25d11a9322

Tx prefix hash: 4f685c3018767907e941254782d29544a9610f85f3d89e654f933da8b219c021
Tx public key: da77164dcf4e3052a1709ee1d0a440fdc86237c13a446cfb9ba7c86b37ab6b5b
Timestamp: 1766139214 Timestamp [UCT]: 2025-12-19 10:13:34 Age [y:d:h:m:s]: 00:003:06:54:11
Block: 1436934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2355 RingCT/type: yes/0
Extra: 01da77164dcf4e3052a1709ee1d0a440fdc86237c13a446cfb9ba7c86b37ab6b5b0211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bfb0bf165a7990d3a5ea704347746f74bfb117e0f1f853103e7f8dda213bdc8 0.600000000000 1925739 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": 1436944, "vin": [ { "gen": { "height": 1436934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bfb0bf165a7990d3a5ea704347746f74bfb117e0f1f853103e7f8dda213bdc8" } } ], "extra": [ 1, 218, 119, 22, 77, 207, 78, 48, 82, 161, 112, 158, 225, 208, 164, 64, 253, 200, 98, 55, 193, 58, 68, 108, 251, 155, 167, 200, 107, 55, 171, 107, 91, 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