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: 9eab92e47a1a215f062047e22577c1d1b4d2d2187d9fa71229b014e2c22466ac
Tx prefix hash: a7de813be9ea936feccb324aeb1209bb5d233e3477eff52e437a418f15eb6451
Tx public key: d284baab935ab9aa1d5dff786d9d677d53271b804dc0eece1a90d9f8c935d488
| Timestamp: 1779475402 | Timestamp [UTC]: 2026-05-22 18:43:22 | Age [y:d:h:m:s]: 00:017:06:52:35 |
| Block: 608 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7278 | RingCT/type: yes/0 |
| Extra: 01d284baab935ab9aa1d5dff786d9d677d53271b804dc0eece1a90d9f8c935d48802090000000493369e7d00 | ||
1 output(s) for total of 35.143660541332 HMNY
| stealth address | amount | amount idx | tag |
| 00: 715a129df3c9d7837f929599ef9688a8f62fb100e7f66b8c516abb51ea9df6f6 | 35.143660541332 | 626 of 0 | <2d> |
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": 668,
"vin": [ {
"gen": {
"height": 608
}
}
],
"vout": [ {
"amount": 35143660541332,
"target": {
"tagged_key": {
"key": "715a129df3c9d7837f929599ef9688a8f62fb100e7f66b8c516abb51ea9df6f6",
"view_tag": "2d"
}
}
}
],
"extra": [ 1, 210, 132, 186, 171, 147, 90, 185, 170, 29, 93, 255, 120, 109, 157, 103, 125, 83, 39, 27, 128, 77, 192, 238, 206, 26, 144, 217, 248, 201, 53, 212, 136, 2, 9, 0, 0, 0, 4, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}