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: 76f8c6e406a6943407a5ae5340aa2ffae0b047cf0e4e481d74e83536a5e5971a
Tx prefix hash: 356e09192359a86021d8ce65b0044bd5e13049d9e6ef05c36f8b49a8ee198482
Tx public key: 2b8861c1cc923cd3f23b1b2d0b02c0233b55e10b096a973421d8db9f87aca49a
| Timestamp: 1779638965 | Timestamp [UTC]: 2026-05-24 16:09:25 | Age [y:d:h:m:s]: 00:015:07:09:28 |
| Block: 1228 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6658 | RingCT/type: yes/0 |
| Extra: 012b8861c1cc923cd3f23b1b2d0b02c0233b55e10b096a973421d8db9f87aca49a020900000001ba6d17be00 | ||
1 output(s) for total of 35.135741313206 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0b28d27e3fbbf2d432241968c0a0107457466759e27a4f0abe60589d4dbe06b7 | 35.135741313206 | 1372 of 0 | <8e> |
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": 1288,
"vin": [ {
"gen": {
"height": 1228
}
}
],
"vout": [ {
"amount": 35135741313206,
"target": {
"tagged_key": {
"key": "0b28d27e3fbbf2d432241968c0a0107457466759e27a4f0abe60589d4dbe06b7",
"view_tag": "8e"
}
}
}
],
"extra": [ 1, 43, 136, 97, 193, 204, 146, 60, 211, 242, 59, 27, 45, 11, 2, 192, 35, 59, 85, 225, 11, 9, 106, 151, 52, 33, 216, 219, 159, 135, 172, 164, 154, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}