Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68f563c2628ff25c35d2df7e1503995b37b2e0de5057f186033d42b71e118278

Tx prefix hash: 91081aaa152cd7ea16e784cd9c956fa16e77551c052d28a210156fdce651ab9f
Tx public key: 0a5dd09d8ec0d62928c37415624470f46c9f788512139ec30f94597e0fb6b054
Timestamp: 1705422681 Timestamp [UCT]: 2024-01-16 16:31:21 Age [y:d:h:m:s]: 00:360:04:31:52
Block: 936685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257883 RingCT/type: yes/0
Extra: 010a5dd09d8ec0d62928c37415624470f46c9f788512139ec30f94597e0fb6b0540211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e09a00f84093b4f4c62436acfcea06efb67264e4fa0a0bcd06a21a441a4e2c3 0.600000000000 1394723 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": 936695, "vin": [ { "gen": { "height": 936685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e09a00f84093b4f4c62436acfcea06efb67264e4fa0a0bcd06a21a441a4e2c3" } } ], "extra": [ 1, 10, 93, 208, 157, 142, 192, 214, 41, 40, 195, 116, 21, 98, 68, 112, 244, 108, 159, 120, 133, 18, 19, 158, 195, 15, 148, 89, 126, 15, 182, 176, 84, 2, 17, 0, 0, 0, 7, 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