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: 68556a48bbe94bb7a6847a0bb464880f8825dac645becebd97eccca6c80601f3
Tx prefix hash: bc38fb84e5630f7fc35ff3e9eaf27230f60c975859396425d74af5f3154dc576
Tx public key: 9e468907b82ff734a7a81e98c0d84e4118cf24e4e8b4e80bfb1fb9c4406e587b
| Timestamp: 1780689074 | Timestamp [UTC]: 2026-06-05 19:51:14 | Age [y:d:h:m:s]: 00:003:04:55:33 |
| Block: 5567 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2319 | RingCT/type: yes/0 |
| Extra: 019e468907b82ff734a7a81e98c0d84e4118cf24e4e8b4e80bfb1fb9c4406e587b020900000001e49593ff00 | ||
1 output(s) for total of 34.812819544358 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8b27e79e1c1f63ca8999e1fe971cc5d7ddbec0df85e8c29504f7311dcb7f595a | 34.812819544358 | 7012 of 0 | <b5> |
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": 5627,
"vin": [ {
"gen": {
"height": 5567
}
}
],
"vout": [ {
"amount": 34812819544358,
"target": {
"tagged_key": {
"key": "8b27e79e1c1f63ca8999e1fe971cc5d7ddbec0df85e8c29504f7311dcb7f595a",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 158, 70, 137, 7, 184, 47, 247, 52, 167, 168, 30, 152, 192, 216, 78, 65, 24, 207, 36, 228, 232, 180, 232, 11, 251, 31, 185, 196, 64, 110, 88, 123, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}