Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dad5976db95fd796e395716300ac3f2cbe3da0aa00eaab647f4be743789a6ff

Tx prefix hash: 0afeeae53c5d5a9907ca5c3330c5433f1ab39550a299f06a0a1a468820e18878
Tx public key: f7b6fd870f48c1a8114403e808483932a8c87e160e5f0d47ebaafcfebaf1bfc4
Timestamp: 1712964919 Timestamp [UCT]: 2024-04-12 23:35:19 Age [y:d:h:m:s]: 00:161:20:11:34
Block: 999205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115954 RingCT/type: yes/0
Extra: 01f7b6fd870f48c1a8114403e808483932a8c87e160e5f0d47ebaafcfebaf1bfc402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 699cc5cc62368d0372967143812ab98aaea8289a7bcf75025dc161c261abc7cf 0.600000000000 1459683 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": 999215, "vin": [ { "gen": { "height": 999205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "699cc5cc62368d0372967143812ab98aaea8289a7bcf75025dc161c261abc7cf" } } ], "extra": [ 1, 247, 182, 253, 135, 15, 72, 193, 168, 17, 68, 3, 232, 8, 72, 57, 50, 168, 200, 126, 22, 14, 95, 13, 71, 235, 170, 252, 254, 186, 241, 191, 196, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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