Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11de43b7b60031c6a71acf145f894f1d09eced7a1bbd27d87466cdffb5f70662

Tx prefix hash: 171bb469d1eaed8fa2649e2ee052b6a796f24db9ae43ace648d5c03267718486
Tx public key: 809b0b8d997ca20a6f5667e8a7abc91be73a4d4938119ce6614f096567791a5a
Timestamp: 1705244670 Timestamp [UCT]: 2024-01-14 15:04:30 Age [y:d:h:m:s]: 01:063:15:27:49
Block: 935222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306571 RingCT/type: yes/0
Extra: 01809b0b8d997ca20a6f5667e8a7abc91be73a4d4938119ce6614f096567791a5a021100000009c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f03d1b917bfd186e62c50a61c274a3b48fa3dd22a77a3267419b4da742518876 0.600000000000 1393238 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": 935232, "vin": [ { "gen": { "height": 935222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f03d1b917bfd186e62c50a61c274a3b48fa3dd22a77a3267419b4da742518876" } } ], "extra": [ 1, 128, 155, 11, 141, 153, 124, 162, 10, 111, 86, 103, 232, 167, 171, 201, 27, 231, 58, 77, 73, 56, 17, 156, 230, 97, 79, 9, 101, 103, 121, 26, 90, 2, 17, 0, 0, 0, 9, 197, 69, 41, 96, 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