Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a24038e5fa549003c82fb6dbf010c4bb54ca3257c63de018cc050b0250027c3e

Tx prefix hash: cba01f1dfc1aea3248bd306ec89efd9b18304afd43816d0168d1d13370370c5f
Tx public key: 14a11bbcf8a1f6128b31e287d1db471688ffbce0f3258a89821c70d96b041c0c
Timestamp: 1695350890 Timestamp [UCT]: 2023-09-22 02:48:10 Age [y:d:h:m:s]: 02:106:18:58:17
Block: 853395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 596077 RingCT/type: yes/0
Extra: 0114a11bbcf8a1f6128b31e287d1db471688ffbce0f3258a89821c70d96b041c0c0211000000014b8f5122000000000000000000

1 output(s) for total of 0.912742253000 dcy

stealth address amount amount idx
00: 093418b704fe455d173e0c84710d839bffa66bf51f4d9f3925ce1b36dc8bcaee 0.912742253000 1307299 of 0

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": 853405, "vin": [ { "gen": { "height": 853395 } } ], "vout": [ { "amount": 912742253, "target": { "key": "093418b704fe455d173e0c84710d839bffa66bf51f4d9f3925ce1b36dc8bcaee" } } ], "extra": [ 1, 20, 161, 27, 188, 248, 161, 246, 18, 139, 49, 226, 135, 209, 219, 71, 22, 136, 255, 188, 224, 243, 37, 138, 137, 130, 28, 112, 217, 107, 4, 28, 12, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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