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: 14e3d14ba94af1decc2e1aee6726adee14dcd85f182ee850f97c5c4f3d2a2e61
Tx prefix hash: 73e59e40e7608805efeac6f5d6d56e2cbbc0c8fc09ab3ba943d5199aea9b7281
Tx public key: ab7d3138e4b915eb60dc3849b41262ed2fc2af33799b5056a5abf7afe80dc632
| Timestamp: 1780836453 | Timestamp [UTC]: 2026-06-07 12:47:33 | Age [y:d:h:m:s]: 00:009:19:34:46 |
| Block: 7413 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1332 | RingCT/type: yes/0 |
| Extra: 01ab7d3138e4b915eb60dc3849b41262ed2fc2af33799b5056a5abf7afe80dc632020900000001e49593ff00 | ||
1 output(s) for total of 34.690460226325 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3a57c8c5350311ee1ac89ba498c55309f6cf445f0297d3551b83aa78e315b7c8 | 34.690460226325 | 9127 of 0 | <04> |
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": 7473,
"vin": [ {
"gen": {
"height": 7413
}
}
],
"vout": [ {
"amount": 34690460226325,
"target": {
"tagged_key": {
"key": "3a57c8c5350311ee1ac89ba498c55309f6cf445f0297d3551b83aa78e315b7c8",
"view_tag": "04"
}
}
}
],
"extra": [ 1, 171, 125, 49, 56, 228, 185, 21, 235, 96, 220, 56, 73, 180, 18, 98, 237, 47, 194, 175, 51, 121, 155, 80, 86, 165, 171, 247, 175, 232, 13, 198, 50, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}