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: 4004e40a8b2bd3e55d526ad65c1118e268bf93819927416d15831f30a7afbd6b
Tx prefix hash: ae41034ff1ad00877df166457b0c659045ace358c5d36eafd00e30b2f991f89d
Tx public key: 454918bc3cd18681fad8a998818b362c93d0216dd86bc2ab9c24f6860506ddde
| Timestamp: 1780082162 | Timestamp [UTC]: 2026-05-29 19:16:02 | Age [y:d:h:m:s]: 00:010:06:19:55 |
| Block: 4777 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3109 | RingCT/type: yes/0 |
| Extra: 01454918bc3cd18681fad8a998818b362c93d0216dd86bc2ab9c24f6860506ddde02090000000226697be300 | ||
1 output(s) for total of 34.865315280092 HMNY
| stealth address | amount | amount idx | tag |
| 00: 27b59da62aa752e6edaefd4fa96e2b7f3fb1fcab178b0043e99da8895f0f03ff | 34.865315280092 | 6004 of 0 | <a1> |
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": 4837,
"vin": [ {
"gen": {
"height": 4777
}
}
],
"vout": [ {
"amount": 34865315280092,
"target": {
"tagged_key": {
"key": "27b59da62aa752e6edaefd4fa96e2b7f3fb1fcab178b0043e99da8895f0f03ff",
"view_tag": "a1"
}
}
}
],
"extra": [ 1, 69, 73, 24, 188, 60, 209, 134, 129, 250, 216, 169, 152, 129, 139, 54, 44, 147, 208, 33, 109, 216, 107, 194, 171, 156, 36, 246, 134, 5, 6, 221, 222, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}