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: a5b4c700baa8ab29ef861fa4f2b99bb02180d7345ba17d0ef473ba9426a5fa7f
Tx prefix hash: b3d33da863611e26502fc7d0596dfca3f3f90875fcdcb868fa2a4151e266c6be
Tx public key: afbe7816e7b36be019f465676b4b528f345a9344aa5a8d0e9df25249d7a6b326
| Timestamp: 1781006539 | Timestamp [UTC]: 2026-06-09 12:02:19 | Age [y:d:h:m:s]: 00:006:06:12:23 |
| Block: 8559 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 186 | RingCT/type: yes/0 |
| Extra: 01afbe7816e7b36be019f465676b4b528f345a9344aa5a8d0e9df25249d7a6b326020900000001e49593ff00 | ||
1 output(s) for total of 34.614715811175 HMNY
| stealth address | amount | amount idx | tag |
| 00: fb6c07181802cb0e6155023d79c849a2afa850e13404266b5c71b3749eee1ce8 | 34.614715811175 | 10569 of 0 | <d6> |
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": 8619,
"vin": [ {
"gen": {
"height": 8559
}
}
],
"vout": [ {
"amount": 34614715811175,
"target": {
"tagged_key": {
"key": "fb6c07181802cb0e6155023d79c849a2afa850e13404266b5c71b3749eee1ce8",
"view_tag": "d6"
}
}
}
],
"extra": [ 1, 175, 190, 120, 22, 231, 179, 107, 224, 25, 244, 101, 103, 107, 75, 82, 143, 52, 90, 147, 68, 170, 90, 141, 14, 157, 242, 82, 73, 215, 166, 179, 38, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}