Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 699673d4aa2ed9731a658233467b8fe28d938522f5bf4c4c06d874dcc0a6dceb

Tx prefix hash: ffb8fa2a0cc03752dad7171f767437e44d749c2b6ff43edb1e0f830fb9ed6685
Tx public key: 907f02ba9b0b0429181dc364e9ebd4e678cce59766f1a5507f92440d28635202
Timestamp: 1674763913 Timestamp [UCT]: 2023-01-26 20:11:53 Age [y:d:h:m:s]: 01:213:11:59:30
Block: 683400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413494 RingCT/type: yes/0
Extra: 01907f02ba9b0b0429181dc364e9ebd4e678cce59766f1a5507f92440d286352020211000000015029cbac000000000000000000

1 output(s) for total of 3.338966369000 dcy

stealth address amount amount idx
00: 22e6dddcd6fa2fd60a0f58b3865aea03fbed0a68b7894bcda30767a8e27cc312 3.338966369000 1125589 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": 683410, "vin": [ { "gen": { "height": 683400 } } ], "vout": [ { "amount": 3338966369, "target": { "key": "22e6dddcd6fa2fd60a0f58b3865aea03fbed0a68b7894bcda30767a8e27cc312" } } ], "extra": [ 1, 144, 127, 2, 186, 155, 11, 4, 41, 24, 29, 195, 100, 233, 235, 212, 230, 120, 204, 229, 151, 102, 241, 165, 80, 127, 146, 68, 13, 40, 99, 82, 2, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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