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: 8f092e4538fd2d7c2425e53074616f4ba4ec5a0a9af75f14e86b8210d00d3e30
Tx prefix hash: 1f630cabd685c51f5c78012b12c4136cfad825ec8cadd370810ec466a9f9b197
Tx public key: 1db183b13dcef5f443cad214cf191a5dcb32d3d098e47576a3445050e3d050b1
| Timestamp: 1779852084 | Timestamp [UTC]: 2026-05-27 03:21:24 | Age [y:d:h:m:s]: 00:012:22:14:33 |
| Block: 2543 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5343 | RingCT/type: yes/0 |
| Extra: 011db183b13dcef5f443cad214cf191a5dcb32d3d098e47576a3445050e3d050b102090000000126697be300 | ||
1 output(s) for total of 35.014194080093 HMNY
| stealth address | amount | amount idx | tag |
| 00: 730b5e1cec1eba6452f1f397827b2530b92958a5e748915dcf616d2458405a4b | 35.014194080093 | 2995 of 0 | <e1> |
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": 2603,
"vin": [ {
"gen": {
"height": 2543
}
}
],
"vout": [ {
"amount": 35014194080093,
"target": {
"tagged_key": {
"key": "730b5e1cec1eba6452f1f397827b2530b92958a5e748915dcf616d2458405a4b",
"view_tag": "e1"
}
}
}
],
"extra": [ 1, 29, 177, 131, 177, 61, 206, 245, 244, 67, 202, 210, 20, 207, 25, 26, 93, 203, 50, 211, 208, 152, 228, 117, 118, 163, 68, 80, 80, 227, 208, 80, 177, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}