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: 2afe904d43cafbf4ae37559fd93331a33c156dc4c00f3614cc07e12fddb4ff72
Tx prefix hash: 3aef4f2883e0a27d0184de880d149e788abb22015c98b0cf0023c83c3c1370f0
Tx public key: bfd92ac9f857ab968cce9e23f771c4272b0293499f4f78696582b0db251a51d2
| Timestamp: 1780081179 | Timestamp [UTC]: 2026-05-29 18:59:39 | Age [y:d:h:m:s]: 00:010:05:47:08 |
| Block: 4770 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3116 | RingCT/type: yes/0 |
| Extra: 01bfd92ac9f857ab968cce9e23f771c4272b0293499f4f78696582b0db251a51d202090000000226697be300 | ||
1 output(s) for total of 34.865780785823 HMNY
| stealth address | amount | amount idx | tag |
| 00: d91748c97c5fe43b63c86b615500603435c9e5441483dbe65c383b562c29661a | 34.865780785823 | 5995 of 0 | <da> |
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": 4830,
"vin": [ {
"gen": {
"height": 4770
}
}
],
"vout": [ {
"amount": 34865780785823,
"target": {
"tagged_key": {
"key": "d91748c97c5fe43b63c86b615500603435c9e5441483dbe65c383b562c29661a",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 191, 217, 42, 201, 248, 87, 171, 150, 140, 206, 158, 35, 247, 113, 196, 39, 43, 2, 147, 73, 159, 79, 120, 105, 101, 130, 176, 219, 37, 26, 81, 210, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}