Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bc7ad5bd39750eddb1ebe703c1a95e3dfbba4a4cec138b6b25829fc0c1a9c29

Tx prefix hash: 7af6f56c63667dd807867f9b4ccde705c4c0c2dd906c1854239950a309de5f98
Tx public key: 8e8d8461d409e0c4afc887579f665fdfe78885e3939381ba756bcca6b5dff7e2
Timestamp: 1705012008 Timestamp [UCT]: 2024-01-11 22:26:48 Age [y:d:h:m:s]: 01:311:03:51:32
Block: 933279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481228 RingCT/type: yes/0
Extra: 018e8d8461d409e0c4afc887579f665fdfe78885e3939381ba756bcca6b5dff7e202110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65efb96b162a18856640274d84e948b7502a7ce769ec608bda7341e00d59368d 0.600000000000 1391241 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": 933289, "vin": [ { "gen": { "height": 933279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65efb96b162a18856640274d84e948b7502a7ce769ec608bda7341e00d59368d" } } ], "extra": [ 1, 142, 141, 132, 97, 212, 9, 224, 196, 175, 200, 135, 87, 159, 102, 95, 223, 231, 136, 133, 227, 147, 147, 129, 186, 117, 107, 204, 166, 181, 223, 247, 226, 2, 17, 0, 0, 0, 13, 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