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: 4b31f513c08e087fdd4f53c9d9d36ef3af8f842f4329a0654effdac67b4d3097
Tx prefix hash: 8878ea8f8194c5fed5fca8833ce5ba21317f1a91f654006a8eb851bc69db2dc4
Tx public key: 1340a4ea99ad3d4e236e3c95bf522f46cfa06ee87d92bb74c8513049ff17b00f
| Timestamp: 1780685873 | Timestamp [UTC]: 2026-06-05 18:57:53 | Age [y:d:h:m:s]: 00:003:05:25:16 |
| Block: 5404 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2482 | RingCT/type: yes/0 |
| Extra: 011340a4ea99ad3d4e236e3c95bf522f46cfa06ee87d92bb74c8513049ff17b00f020900000001e49593ff00 | ||
1 output(s) for total of 34.823644467270 HMNY
| stealth address | amount | amount idx | tag |
| 00: 38326c329aa0e3f0ddc53201c365d15f69b167bd20d487c937bd5f75b8675f7e | 34.823644467270 | 6841 of 0 | <27> |
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": 5464,
"vin": [ {
"gen": {
"height": 5404
}
}
],
"vout": [ {
"amount": 34823644467270,
"target": {
"tagged_key": {
"key": "38326c329aa0e3f0ddc53201c365d15f69b167bd20d487c937bd5f75b8675f7e",
"view_tag": "27"
}
}
}
],
"extra": [ 1, 19, 64, 164, 234, 153, 173, 61, 78, 35, 110, 60, 149, 191, 82, 47, 70, 207, 160, 110, 232, 125, 146, 187, 116, 200, 81, 48, 73, 255, 23, 176, 15, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}