Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89f6214c17b6d11c2c5a1365b9354c2417890dd0bc98adb58ffdcfa4acd19267

Tx prefix hash: c044d9869db5d2e94172eecebbbac0a6f54896e522495b4f99b9daf74c979299
Tx public key: 538e0b0a90d9a765a14661128b281deb2e5c84cb41ed98ae79d8cb3f07fec72c
Timestamp: 1728542383 Timestamp [UCT]: 2024-10-10 06:39:43 Age [y:d:h:m:s]: 00:166:10:54:11
Block: 1128378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118745 RingCT/type: yes/0
Extra: 01538e0b0a90d9a765a14661128b281deb2e5c84cb41ed98ae79d8cb3f07fec72c02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d82984f23f3fc00031c841ec4b2838b316a6f8856caafc0e141e70ba2acdfec7 0.600000000000 1611195 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": 1128388, "vin": [ { "gen": { "height": 1128378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d82984f23f3fc00031c841ec4b2838b316a6f8856caafc0e141e70ba2acdfec7" } } ], "extra": [ 1, 83, 142, 11, 10, 144, 217, 167, 101, 161, 70, 97, 18, 139, 40, 29, 235, 46, 92, 132, 203, 65, 237, 152, 174, 121, 216, 203, 63, 7, 254, 199, 44, 2, 17, 0, 0, 0, 4, 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