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: 368dc584e38031c962e19e6771711774592fe31dd9f04e6a2ef77de865ce908a
Tx prefix hash: 528411da6e0e592c9777cce143c5754d2b628a0dfe6fa29403a6aef2544b4a6f
Tx public key: 8d7c32d4e81a6322ae6e826201fa1c0111fe5c63486ecedbff06abfd733dfdd0
| Timestamp: 1779475746 | Timestamp [UTC]: 2026-05-22 18:49:06 | Age [y:d:h:m:s]: 00:017:06:46:51 |
| Block: 610 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7276 | RingCT/type: yes/0 |
| Extra: 018d7c32d4e81a6322ae6e826201fa1c0111fe5c63486ecedbff06abfd733dfdd002090000000293369e7d00 | ||
1 output(s) for total of 35.143526479034 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5c35af1ec86c183abaedfef84f930c24ee73a1cbfe8e5f57c2ac2b1d7f10e583 | 35.143526479034 | 628 of 0 | <13> |
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": 670,
"vin": [ {
"gen": {
"height": 610
}
}
],
"vout": [ {
"amount": 35143526479034,
"target": {
"tagged_key": {
"key": "5c35af1ec86c183abaedfef84f930c24ee73a1cbfe8e5f57c2ac2b1d7f10e583",
"view_tag": "13"
}
}
}
],
"extra": [ 1, 141, 124, 50, 212, 232, 26, 99, 34, 174, 110, 130, 98, 1, 250, 28, 1, 17, 254, 92, 99, 72, 110, 206, 219, 255, 6, 171, 253, 115, 61, 253, 208, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}