Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e39c9afb2304b5e0ecad0f8fbbd2067a45bbc0bd227efd41c3be5763da9802f

Tx prefix hash: 0b87688ab23146b2ec3ad32d5c0497cfe20d512a2f6c81cd4eb16b4069c9a3da
Tx public key: 52109dcd26597cc41e7e7517069a7f84fee9d85a4b59614028f64c7a05027396
Timestamp: 1719808683 Timestamp [UCT]: 2024-07-01 04:38:03 Age [y:d:h:m:s]: 01:169:09:16:59
Block: 1055967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379643 RingCT/type: yes/0
Extra: 0152109dcd26597cc41e7e7517069a7f84fee9d85a4b59614028f64c7a050273960211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d781280975db803a900e5ae44aabd4e09989f322af74f0ad01dd13a23a8e0d3 0.600000000000 1526378 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": 1055977, "vin": [ { "gen": { "height": 1055967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d781280975db803a900e5ae44aabd4e09989f322af74f0ad01dd13a23a8e0d3" } } ], "extra": [ 1, 82, 16, 157, 205, 38, 89, 124, 196, 30, 126, 117, 23, 6, 154, 127, 132, 254, 233, 216, 90, 75, 89, 97, 64, 40, 246, 76, 122, 5, 2, 115, 150, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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