For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: f8368365dc75a17ae9c094a75f3683d08596880787a0d40b2f40fdbd8fe8f9f7
Tx prefix hash: 5b36849ccb7b055e9555ffdd889ffe8bedf357bea943e8c351f1f4ba36c513ea
Tx public key: 4f262f8b3fd6063bceb1e3f76cf25a5a77ad5f4b4ff07b777bd714f297bd61ef
| Timestamp: 1780807754 | Timestamp [UTC]: 2026-06-07 04:49:14 | Age [y:d:h:m:s]: 00:001:20:46:43 |
| Block: 6972 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 914 | RingCT/type: yes/0 |
| Extra: 014f262f8b3fd6063bceb1e3f76cf25a5a77ad5f4b4ff07b777bd714f297bd61ef020900000001e49593ff00 | ||
1 output(s) for total of 34.719652089307 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3b82ea658970c2a295ab41b7d1a6a76fc4844ff9ad6b656122a6d867b4a0c09a | 34.719652089307 | 8598 of 0 | <74> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 7032,
"vin": [ {
"gen": {
"height": 6972
}
}
],
"vout": [ {
"amount": 34719652089307,
"target": {
"tagged_key": {
"key": "3b82ea658970c2a295ab41b7d1a6a76fc4844ff9ad6b656122a6d867b4a0c09a",
"view_tag": "74"
}
}
}
],
"extra": [ 1, 79, 38, 47, 139, 63, 214, 6, 59, 206, 177, 227, 247, 108, 242, 90, 90, 119, 173, 95, 75, 79, 240, 123, 119, 123, 215, 20, 242, 151, 189, 97, 239, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}