Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 338d42ba6bc8556b33e846fc1154472fbd03f07f47cc8e5c3e8887d4e354b333

Tx prefix hash: fa82dc29dbf63d384eb74c458ad7df89c21f0104f32d56f02ede338dd404b7d6
Tx public key: e6411564c4a962f7b8903995048455beb5042892caa5f3b0b7c159412d6b2c32
Timestamp: 1705504109 Timestamp [UCT]: 2024-01-17 15:08:29 Age [y:d:h:m:s]: 01:078:22:50:26
Block: 937362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317519 RingCT/type: yes/0
Extra: 01e6411564c4a962f7b8903995048455beb5042892caa5f3b0b7c159412d6b2c320211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b6dfacd666589fc2b71360d8c769741c6460bf22ed6f99a58a01791eccbe979 0.600000000000 1395414 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": 937372, "vin": [ { "gen": { "height": 937362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b6dfacd666589fc2b71360d8c769741c6460bf22ed6f99a58a01791eccbe979" } } ], "extra": [ 1, 230, 65, 21, 100, 196, 169, 98, 247, 184, 144, 57, 149, 4, 132, 85, 190, 181, 4, 40, 146, 202, 165, 243, 176, 183, 193, 89, 65, 45, 107, 44, 50, 2, 17, 0, 0, 0, 7, 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