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: 762843420e7194bee979fb576c8c16d2a6ea68bfb3ba8551f63e6965b310ecd5
Tx prefix hash: 3f19f5525d3d8edb28234471b8ab2b7966285bedfc7b85bb244e2596449d2b3f
Tx public key: 8a740a15bf02fddaff2cd2a7064d45d1ccdd3f13762d8f17401b55d5d01ace8f
| Timestamp: 1779940841 | Timestamp [UTC]: 2026-05-28 04:00:41 | Age [y:d:h:m:s]: 00:011:20:46:06 |
| Block: 3490 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4396 | RingCT/type: yes/0 |
| Extra: 018a740a15bf02fddaff2cd2a7064d45d1ccdd3f13762d8f17401b55d5d01ace8f02090000000126697be300 | ||
1 output(s) for total of 34.951006395058 HMNY
| stealth address | amount | amount idx | tag |
| 00: fa50083b94ac2448f5da46854264b433a4bfe92f74f57d411a599c1fc28fb4fa | 34.951006395058 | 4209 of 0 | <5b> |
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": 3550,
"vin": [ {
"gen": {
"height": 3490
}
}
],
"vout": [ {
"amount": 34951006395058,
"target": {
"tagged_key": {
"key": "fa50083b94ac2448f5da46854264b433a4bfe92f74f57d411a599c1fc28fb4fa",
"view_tag": "5b"
}
}
}
],
"extra": [ 1, 138, 116, 10, 21, 191, 2, 253, 218, 255, 44, 210, 167, 6, 77, 69, 209, 204, 221, 63, 19, 118, 45, 143, 23, 64, 27, 85, 213, 208, 26, 206, 143, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}