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: 9851ab9c98ce5b007694d382fc7e875a5cb7f8a13d35055107479fee82dca4bf
Tx prefix hash: 74d0a64ed6475d7b2aa0f6f94fedf1f879a9f087c1560cce3723b809eaead27b
Tx public key: f1e240306171acbd460516c6a88031a892b6f42e951d5bf48808bcd499548396
| Timestamp: 1779966570 | Timestamp [UTC]: 2026-05-28 11:09:30 | Age [y:d:h:m:s]: 00:011:13:37:17 |
| Block: 3813 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4073 | RingCT/type: yes/0 |
| Extra: 01f1e240306171acbd460516c6a88031a892b6f42e951d5bf48808bcd49954839602090000000426697be300 | ||
1 output(s) for total of 34.929480613316 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4e41dee12810b764193a7860c201fcc9fcfd38c28c6b455e8d8c3c40b0d6f79a | 34.929480613316 | 4642 of 0 | <5e> |
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": 3873,
"vin": [ {
"gen": {
"height": 3813
}
}
],
"vout": [ {
"amount": 34929480613316,
"target": {
"tagged_key": {
"key": "4e41dee12810b764193a7860c201fcc9fcfd38c28c6b455e8d8c3c40b0d6f79a",
"view_tag": "5e"
}
}
}
],
"extra": [ 1, 241, 226, 64, 48, 97, 113, 172, 189, 70, 5, 22, 198, 168, 128, 49, 168, 146, 182, 244, 46, 149, 29, 91, 244, 136, 8, 188, 212, 153, 84, 131, 150, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}