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: 377560313411a725ad83334cb273aee18b2ac97b071402e074017a6479d7d119
Tx prefix hash: a3c047ab81f06e2e18d725acf0bdebbc34075fe55e756017177bd5577320c489
Tx public key: 5840216c0f7e60a1adc8617373e664734963d935fc223ea8902b2d188569ff4d
| Timestamp: 1780322710 | Timestamp [UTC]: 2026-06-01 14:05:10 | Age [y:d:h:m:s]: 00:007:12:44:38 |
| Block: 5009 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2891 | RingCT/type: yes/0 |
| Extra: 015840216c0f7e60a1adc8617373e664734963d935fc223ea8902b2d188569ff4d02090000002e26697be300 | ||
1 output(s) for total of 34.849890606128 HMNY
| stealth address | amount | amount idx | tag |
| 00: 97f866adcc680420d3ed76e3df9eca321fa3d78fd91fb5f09ed69a9e0f61c105 | 34.849890606128 | 6382 of 0 | <c2> |
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": 5069,
"vin": [ {
"gen": {
"height": 5009
}
}
],
"vout": [ {
"amount": 34849890606128,
"target": {
"tagged_key": {
"key": "97f866adcc680420d3ed76e3df9eca321fa3d78fd91fb5f09ed69a9e0f61c105",
"view_tag": "c2"
}
}
}
],
"extra": [ 1, 88, 64, 33, 108, 15, 126, 96, 161, 173, 200, 97, 115, 115, 230, 100, 115, 73, 99, 217, 53, 252, 34, 62, 168, 144, 43, 45, 24, 133, 105, 255, 77, 2, 9, 0, 0, 0, 46, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}