Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0696ed2a17fcc3c1c1b2f05c26eb83f57f0a4419eb8b59eb7e8477ed14a84c6c

Tx prefix hash: 04c875ca27a8357cf5e2025f68affad9f415ce2ffb0e7738cca56859f01b1227
Tx public key: e62062dbaacdd37469159032d580bbf8018fd5dea410f78a378a5e21f03b931b
Timestamp: 1698512906 Timestamp [UCT]: 2023-10-28 17:08:26 Age [y:d:h:m:s]: 02:074:00:04:09
Block: 879631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 572555 RingCT/type: yes/0
Extra: 01e62062dbaacdd37469159032d580bbf8018fd5dea410f78a378a5e21f03b931b021100000007faf35c9c000000000000000000

1 output(s) for total of 0.747166442000 dcy

stealth address amount amount idx
00: 0ea4b4dec6954c79a353eb1c317f0cd4e09616224769e738814a8710f8680188 0.747166442000 1335165 of 0

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": 879641, "vin": [ { "gen": { "height": 879631 } } ], "vout": [ { "amount": 747166442, "target": { "key": "0ea4b4dec6954c79a353eb1c317f0cd4e09616224769e738814a8710f8680188" } } ], "extra": [ 1, 230, 32, 98, 219, 170, 205, 211, 116, 105, 21, 144, 50, 213, 128, 187, 248, 1, 143, 213, 222, 164, 16, 247, 138, 55, 138, 94, 33, 240, 59, 147, 27, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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