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: 52328e1dd8c183dd0a3d4cbc25f0af776b3ee756e6f526c871ef9c139d5093a2
Tx prefix hash: b8e644a8e08394e4cfe7ea1f82d1094267c171ec3556eb3558993f4bf2084f84
Tx public key: 94ca6c8adccb21d6f71162412325895710e7b0831054848b6d23a4341df8be3d
| Timestamp: 1780701548 | Timestamp [UTC]: 2026-06-05 23:19:08 | Age [y:d:h:m:s]: 00:003:02:16:49 |
| Block: 6061 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1825 | RingCT/type: yes/0 |
| Extra: 0194ca6c8adccb21d6f71162412325895710e7b0831054848b6d23a4341df8be3d020900000002e49593ff00 | ||
1 output(s) for total of 34.780033270847 HMNY
| stealth address | amount | amount idx | tag |
| 00: d9f57db42952f8335beced921153992a8044e7969610c15a6833c4bf699a6ec5 | 34.780033270847 | 7530 of 0 | <e6> |
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": 6121,
"vin": [ {
"gen": {
"height": 6061
}
}
],
"vout": [ {
"amount": 34780033270847,
"target": {
"tagged_key": {
"key": "d9f57db42952f8335beced921153992a8044e7969610c15a6833c4bf699a6ec5",
"view_tag": "e6"
}
}
}
],
"extra": [ 1, 148, 202, 108, 138, 220, 203, 33, 214, 247, 17, 98, 65, 35, 37, 137, 87, 16, 231, 176, 131, 16, 84, 132, 139, 109, 35, 164, 52, 29, 248, 190, 61, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}