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: 327d1aa01cf81b879cef927bab5d1f45d8271e95aed662202ff8a1c10dad4afd
Tx prefix hash: 71a5da76620f7b2fc9132bc21ea4023400fa2e1979a5fd5e2ce4146dbd3cd528
Tx public key: e58bb047f6f13c6018a8aadf914fb4f70cc59302861fae76c83ecef6141c70d9
| Timestamp: 1780821788 | Timestamp [UTC]: 2026-06-07 08:43:08 | Age [y:d:h:m:s]: 00:001:16:52:49 |
| Block: 7185 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 701 | RingCT/type: yes/0 |
| Extra: 01e58bb047f6f13c6018a8aadf914fb4f70cc59302861fae76c83ecef6141c70d9020900000001e49593ff00 | ||
1 output(s) for total of 34.705549552296 HMNY
| stealth address | amount | amount idx | tag |
| 00: e56142cac6416b9ea7088dd816ade7cfe1465cf1edd0b592ec47ac3dfc1ba54c | 34.705549552296 | 8851 of 0 | <ec> |
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": 7245,
"vin": [ {
"gen": {
"height": 7185
}
}
],
"vout": [ {
"amount": 34705549552296,
"target": {
"tagged_key": {
"key": "e56142cac6416b9ea7088dd816ade7cfe1465cf1edd0b592ec47ac3dfc1ba54c",
"view_tag": "ec"
}
}
}
],
"extra": [ 1, 229, 139, 176, 71, 246, 241, 60, 96, 24, 168, 170, 223, 145, 79, 180, 247, 12, 197, 147, 2, 134, 31, 174, 118, 200, 62, 206, 246, 20, 28, 112, 217, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}