Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d19494ace63a301c942a4d9000c5620d1b526046c517a77c0858736ad477c7df

Tx prefix hash: c430af48eb38b2f80d9b67edc1b8485572489b1eacc2a33caceb0a89db4b808c
Tx public key: 1edf87eff5ef643e46b19a363f4c05f5054c211cb2108a40a059a519c26ec305
Timestamp: 1721777983 Timestamp [UCT]: 2024-07-23 23:39:43 Age [y:d:h:m:s]: 00:214:19:16:36
Block: 1072289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153401 RingCT/type: yes/0
Extra: 011edf87eff5ef643e46b19a363f4c05f5054c211cb2108a40a059a519c26ec30502110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02b0c193c974e49413a83f644a15f7813a60be264793e49c83e6217a4f2f48d3 0.600000000000 1544750 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": 1072299, "vin": [ { "gen": { "height": 1072289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02b0c193c974e49413a83f644a15f7813a60be264793e49c83e6217a4f2f48d3" } } ], "extra": [ 1, 30, 223, 135, 239, 245, 239, 100, 62, 70, 177, 154, 54, 63, 76, 5, 245, 5, 76, 33, 28, 178, 16, 138, 64, 160, 89, 165, 25, 194, 110, 195, 5, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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