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: 719734d5ab8d06576c9468704a7b966a306d69674ca9b60d0d1d9eb376e08cee
Tx prefix hash: 0c1973ef9a3e1b5352ce7d0b3143d1efa7dc3faba6054e4a23cff5397dc0f071
Tx public key: 9e8d61ec0361bb2f822435ca24d9d45aa14dc7fce32e7426962d2c52761391f5
| Timestamp: 1779802506 | Timestamp [UTC]: 2026-05-26 13:35:06 | Age [y:d:h:m:s]: 00:013:12:00:51 |
| Block: 2315 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5571 | RingCT/type: yes/0 |
| Extra: 019e8d61ec0361bb2f822435ca24d9d45aa14dc7fce32e7426962d2c52761391f502090000000226697be300 | ||
1 output(s) for total of 35.029424220732 HMNY
| stealth address | amount | amount idx | tag |
| 00: b60d2edf73e73a2fd9ea546b4fd76f853a46ea2497e0b025c611622b02ff2ed5 | 35.029424220732 | 2705 of 0 | <22> |
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": 2375,
"vin": [ {
"gen": {
"height": 2315
}
}
],
"vout": [ {
"amount": 35029424220732,
"target": {
"tagged_key": {
"key": "b60d2edf73e73a2fd9ea546b4fd76f853a46ea2497e0b025c611622b02ff2ed5",
"view_tag": "22"
}
}
}
],
"extra": [ 1, 158, 141, 97, 236, 3, 97, 187, 47, 130, 36, 53, 202, 36, 217, 212, 90, 161, 77, 199, 252, 227, 46, 116, 38, 150, 45, 44, 82, 118, 19, 145, 245, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}