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: db394bf8983d9f28455b69d317072dc9a0796f819aef70db4ce5fb0bcab9b52b
Tx prefix hash: 24084d8c905077ee2b7d5c784e677f9b0e2fd1ff64fefd9698084a930b54fc2c
Tx public key: 1a8b84626b61b1268e2f1951cdda25a069be1ac9df1df3bd3e4dfcc1d5987cfa
| Timestamp: 1779629196 | Timestamp [UTC]: 2026-05-24 13:26:36 | Age [y:d:h:m:s]: 00:023:19:02:36 |
| Block: 818 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7927 | RingCT/type: yes/0 |
| Extra: 011a8b84626b61b1268e2f1951cdda25a069be1ac9df1df3bd3e4dfcc1d5987cfa020900000001ba6d17be00 | ||
1 output(s) for total of 35.129586791965 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2f423f9ffaafd165d5aa8b4c4736e057962f3c19ec87c5612b54f96fd1683e0a | 35.129586791965 | 950 of 0 | <58> |
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": 878,
"vin": [ {
"gen": {
"height": 818
}
}
],
"vout": [ {
"amount": 35129586791965,
"target": {
"tagged_key": {
"key": "2f423f9ffaafd165d5aa8b4c4736e057962f3c19ec87c5612b54f96fd1683e0a",
"view_tag": "58"
}
}
}
],
"extra": [ 1, 26, 139, 132, 98, 107, 97, 177, 38, 142, 47, 25, 81, 205, 218, 37, 160, 105, 190, 26, 201, 223, 29, 243, 189, 62, 77, 252, 193, 213, 152, 124, 250, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}