Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04d13c5b9f222791dba39c594839c1947a89ecd1bdf9ff9d9d70274e160c14df

Tx prefix hash: 1601562b6209f117446cac60d8c77d01b67548dcf745aafdf24a5e9af0e24363
Tx public key: c5337a96615c7eb5c99276f8d5bc954ff9b88e96c8110aec24127fce5f97d5dc
Timestamp: 1710672603 Timestamp [UCT]: 2024-03-17 10:50:03 Age [y:d:h:m:s]: 00:298:11:34:35
Block: 980243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213653 RingCT/type: yes/0
Extra: 01c5337a96615c7eb5c99276f8d5bc954ff9b88e96c8110aec24127fce5f97d5dc0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50cab795f9d745e9615b635aa49c20482126afd2b1c9f8595758aa0e33637209 0.600000000000 1440308 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": 980253, "vin": [ { "gen": { "height": 980243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50cab795f9d745e9615b635aa49c20482126afd2b1c9f8595758aa0e33637209" } } ], "extra": [ 1, 197, 51, 122, 150, 97, 92, 126, 181, 201, 146, 118, 248, 213, 188, 149, 79, 249, 184, 142, 150, 200, 17, 10, 236, 36, 18, 127, 206, 95, 151, 213, 220, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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