Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 433db43f12d5b34a6760a6fe52c8dae2410209bc1ecee63465f1d2f6b50c62df

Tx prefix hash: 02043bf8b784fe17eb61ae6fe3fd7b1c735ddce277c7a8cc63e2812b7ff799fb
Tx public key: 79a98d99143f50e36467fa8904af25ecfee434b99be6a9da229042c16573c9f2
Timestamp: 1613170741 Timestamp [UCT]: 2021-02-12 22:59:01 Age [y:d:h:m:s]: 03:358:11:53:58
Block: 197614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1014979 RingCT/type: yes/0
Extra: 0179a98d99143f50e36467fa8904af25ecfee434b99be6a9da229042c16573c9f20211000001dbdf1e48bb000000000000000000

1 output(s) for total of 135.901237431000 dcy

stealth address amount amount idx
00: be64c0fab2326f81137dfe5e21045cc01f6b3a1a7c5b0be12c5ff636889b747f 135.901237431000 404280 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": 197624, "vin": [ { "gen": { "height": 197614 } } ], "vout": [ { "amount": 135901237431, "target": { "key": "be64c0fab2326f81137dfe5e21045cc01f6b3a1a7c5b0be12c5ff636889b747f" } } ], "extra": [ 1, 121, 169, 141, 153, 20, 63, 80, 227, 100, 103, 250, 137, 4, 175, 37, 236, 254, 228, 52, 185, 155, 230, 169, 218, 34, 144, 66, 193, 101, 115, 201, 242, 2, 17, 0, 0, 1, 219, 223, 30, 72, 187, 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