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: fa381482ec55ea7ceed7437662d86473df87c4942889d2f7e60403ccd92c59af
Tx prefix hash: 6fcde8f213c96bc033a58fb4ba3929911130732751864b60a58d386b84a41b68
Tx public key: 4f672b0e79b8eb4c0d713966d89c6ca7abcd7ffef4951d6c34949c5b84f460c1
| Timestamp: 1780384045 | Timestamp [UTC]: 2026-06-02 07:07:25 | Age [y:d:h:m:s]: 00:006:17:39:22 |
| Block: 5167 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2719 | RingCT/type: yes/0 |
| Extra: 014f672b0e79b8eb4c0d713966d89c6ca7abcd7ffef4951d6c34949c5b84f460c102090000000126697be300 | ||
1 output(s) for total of 34.839389777653 HMNY
| stealth address | amount | amount idx | tag |
| 00: 77a40705a7d94fdb0b69c95107b33e1804c322b42dd976d2d96619a3d0727f09 | 34.839389777653 | 6546 of 0 | <50> |
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": 5227,
"vin": [ {
"gen": {
"height": 5167
}
}
],
"vout": [ {
"amount": 34839389777653,
"target": {
"tagged_key": {
"key": "77a40705a7d94fdb0b69c95107b33e1804c322b42dd976d2d96619a3d0727f09",
"view_tag": "50"
}
}
}
],
"extra": [ 1, 79, 103, 43, 14, 121, 184, 235, 76, 13, 113, 57, 102, 216, 156, 108, 167, 171, 205, 127, 254, 244, 149, 29, 108, 52, 148, 156, 91, 132, 244, 96, 193, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}