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: 77d6b9b164c426cc69ac02cba2d01e7c1892654bb6a92464fc77fb9a3a1642b2
Tx prefix hash: e0ce8c36f5e18aa8d328946d6e43a57cdb10f960da2580e308c800d3c6f5c5bf
Tx public key: a72b577cc0a3b2f0e5fb1c3b741a981ebe9e1e917666576af20bed7325e39989
| Timestamp: 1779444110 | Timestamp [UTC]: 2026-05-22 10:01:50 | Age [y:d:h:m:s]: 00:017:15:34:07 |
| Block: 246 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7640 | RingCT/type: yes/0 |
| Extra: 01a72b577cc0a3b2f0e5fb1c3b741a981ebe9e1e917666576af20bed7325e399890209000000024438f87f00 | ||
1 output(s) for total of 35.167934242594 HMNY
| stealth address | amount | amount idx | tag |
| 00: a00a56882520537dc3464f1a620d11b8efd63c735e065c1a4e5595d4c774ab68 | 35.167934242594 | 242 of 0 | <7a> |
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": 306,
"vin": [ {
"gen": {
"height": 246
}
}
],
"vout": [ {
"amount": 35167934242594,
"target": {
"tagged_key": {
"key": "a00a56882520537dc3464f1a620d11b8efd63c735e065c1a4e5595d4c774ab68",
"view_tag": "7a"
}
}
}
],
"extra": [ 1, 167, 43, 87, 124, 192, 163, 178, 240, 229, 251, 28, 59, 116, 26, 152, 30, 190, 158, 30, 145, 118, 102, 87, 106, 242, 11, 237, 115, 37, 227, 153, 137, 2, 9, 0, 0, 0, 2, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}