Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ef7d82fad29ca38d899d9e08b63cde3c0007719b2d65c3ed8217da0be7f53c9

Tx prefix hash: 37ec769c65ae30c2496e2d83ae23e9ea14798db3545f70d7ba843b671df9601b
Tx public key: 8e81e36f8babfefadd4dd2c5e1540ba79303e48fc5a922aaf525b9f110385e3b
Timestamp: 1716502802 Timestamp [UCT]: 2024-05-23 22:20:02 Age [y:d:h:m:s]: 00:160:23:07:12
Block: 1028568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115213 RingCT/type: yes/0
Extra: 018e81e36f8babfefadd4dd2c5e1540ba79303e48fc5a922aaf525b9f110385e3b02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4a4f4eccf39c285d5aae0f9427cb5525dd34f5f6a0cb9b98bddf18685e3fcd2 0.600000000000 1496561 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": 1028578, "vin": [ { "gen": { "height": 1028568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4a4f4eccf39c285d5aae0f9427cb5525dd34f5f6a0cb9b98bddf18685e3fcd2" } } ], "extra": [ 1, 142, 129, 227, 111, 139, 171, 254, 250, 221, 77, 210, 197, 225, 84, 11, 167, 147, 3, 228, 143, 197, 169, 34, 170, 245, 37, 185, 241, 16, 56, 94, 59, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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