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: 704ce945740d6b984cad494e0362dcc140ee8b551ed66a7eda613844cbfbf23b
Tx prefix hash: 391c1a1b31dfe21a8d211f8287588e3275d563db3d2ff9e172be4c723ba5a98c
Tx public key: 4f7a16bce8b97c933c61466cb4adbd750af4b2c9f9b09d8cd2c5fb6fb4bfe7b3
| Timestamp: 1780323387 | Timestamp [UTC]: 2026-06-01 14:16:27 | Age [y:d:h:m:s]: 00:007:13:34:31 |
| Block: 5125 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2828 | RingCT/type: yes/0 |
| Extra: 014f7a16bce8b97c933c61466cb4adbd750af4b2c9f9b09d8cd2c5fb6fb4bfe7b302090000004026697be300 | ||
1 output(s) for total of 34.842180828331 HMNY
| stealth address | amount | amount idx | tag |
| 00: 32c4285940f878b7e804f48f2f3066799901828abe3ba2b88dab1ccde705eb64 | 34.842180828331 | 6500 of 0 | <b8> |
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": 5185,
"vin": [ {
"gen": {
"height": 5125
}
}
],
"vout": [ {
"amount": 34842180828331,
"target": {
"tagged_key": {
"key": "32c4285940f878b7e804f48f2f3066799901828abe3ba2b88dab1ccde705eb64",
"view_tag": "b8"
}
}
}
],
"extra": [ 1, 79, 122, 22, 188, 232, 185, 124, 147, 60, 97, 70, 108, 180, 173, 189, 117, 10, 244, 178, 201, 249, 176, 157, 140, 210, 197, 251, 111, 180, 191, 231, 179, 2, 9, 0, 0, 0, 64, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}