Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5593a65ca36194ae26f0df04999f248833ea40a5179c1f17d19e675af449001

Tx prefix hash: 614b7b9a3ccf7cca8eee6b48190b54f225f9d2161afb2d8c9e2351b3483507ba
Tx public key: 59933444b16b9ea05f0212dc7e63c67749fc887c0b2c955179c73ab8ac6f9d79
Timestamp: 1716099343 Timestamp [UCT]: 2024-05-19 06:15:43 Age [y:d:h:m:s]: 01:030:03:10:04
Block: 1025222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282346 RingCT/type: yes/0
Extra: 0159933444b16b9ea05f0212dc7e63c67749fc887c0b2c955179c73ab8ac6f9d790211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd646bf527a3a77cd84aca8858f90c4ffd13c914a4da800ba4f311a8428d0d35 0.600000000000 1491567 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": 1025232, "vin": [ { "gen": { "height": 1025222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd646bf527a3a77cd84aca8858f90c4ffd13c914a4da800ba4f311a8428d0d35" } } ], "extra": [ 1, 89, 147, 52, 68, 177, 107, 158, 160, 95, 2, 18, 220, 126, 99, 198, 119, 73, 252, 136, 124, 11, 44, 149, 81, 121, 199, 58, 184, 172, 111, 157, 121, 2, 17, 0, 0, 0, 2, 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