Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65ed51f39cbfaf56c69e20330fcc790bebd4a9f100ef34cccc06c49312c7a30b

Tx prefix hash: 3217ffb7fb76b81eee13e8323e43c6a785fffdc02cc4feb2e9d934f65e263c0c
Tx public key: f14f8ce4500b371a339a5dbb5edce668f2c9fc817e1a366cf3e2110668702932
Timestamp: 1719899459 Timestamp [UCT]: 2024-07-02 05:50:59 Age [y:d:h:m:s]: 00:281:12:46:24
Block: 1056725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201153 RingCT/type: yes/0
Extra: 01f14f8ce4500b371a339a5dbb5edce668f2c9fc817e1a366cf3e211066870293202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4475f069b54cb8f57914ea0c616a30ef404a0c6a2a193a48ced6ef7408cef197 0.600000000000 1527146 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": 1056735, "vin": [ { "gen": { "height": 1056725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4475f069b54cb8f57914ea0c616a30ef404a0c6a2a193a48ced6ef7408cef197" } } ], "extra": [ 1, 241, 79, 140, 228, 80, 11, 55, 26, 51, 154, 93, 187, 94, 220, 230, 104, 242, 201, 252, 129, 126, 26, 54, 108, 243, 226, 17, 6, 104, 112, 41, 50, 2, 17, 0, 0, 0, 2, 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