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: 55be656780eaad8b58519bfb7439862c2378069e3b207bb6fed097c665460b11
Tx prefix hash: 332f39dd7fc599b04e5799799b9c00cc374a401f5205f0a0e321479e896e2866
Tx public key: 538e1084a76898b7e6e935c5ba62bc1a010f1c54836bcf7cc33ed04bbf66b2c4
| Timestamp: 1780814115 | Timestamp [UTC]: 2026-06-07 06:35:15 | Age [y:d:h:m:s]: 00:001:19:00:42 |
| Block: 7025 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 861 | RingCT/type: yes/0 |
| Extra: 01538e1084a76898b7e6e935c5ba62bc1a010f1c54836bcf7cc33ed04bbf66b2c4020900000001e49593ff00 | ||
1 output(s) for total of 34.716142471866 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7ed6be24907df053fd87e758296f0894bc2db4e960f28dce98a61f5b340af6bb | 34.716142471866 | 8665 of 0 | <9e> |
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": 7085,
"vin": [ {
"gen": {
"height": 7025
}
}
],
"vout": [ {
"amount": 34716142471866,
"target": {
"tagged_key": {
"key": "7ed6be24907df053fd87e758296f0894bc2db4e960f28dce98a61f5b340af6bb",
"view_tag": "9e"
}
}
}
],
"extra": [ 1, 83, 142, 16, 132, 167, 104, 152, 183, 230, 233, 53, 197, 186, 98, 188, 26, 1, 15, 28, 84, 131, 107, 207, 124, 195, 62, 208, 75, 191, 102, 178, 196, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}