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: d4901abe695b59809811ed4d63ffd8ead54f4ddb8f094d766122b6ead4befd03
Tx prefix hash: 9e8e1ead46ddc74cc45e115cd91849484ffcf371c52b16bf997f879db4b750b7
Tx public key: 862cf21acf828216b02c7b217e92e9ff2e3adee240fad71fda1214f172e4845d
| Timestamp: 1780133480 | Timestamp [UTC]: 2026-05-30 09:31:20 | Age [y:d:h:m:s]: 00:009:13:47:33 |
| Block: 4953 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2933 | RingCT/type: yes/0 |
| Extra: 01862cf21acf828216b02c7b217e92e9ff2e3adee240fad71fda1214f172e4845d02090000000126697be300 | ||
1 output(s) for total of 34.853613178388 HMNY
| stealth address | amount | amount idx | tag |
| 00: f90d85b704f2598f32e4a49b714365385dfc0a2ae03f78e90a556d91bb9a628d | 34.853613178388 | 6296 of 0 | <a6> |
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": 5013,
"vin": [ {
"gen": {
"height": 4953
}
}
],
"vout": [ {
"amount": 34853613178388,
"target": {
"tagged_key": {
"key": "f90d85b704f2598f32e4a49b714365385dfc0a2ae03f78e90a556d91bb9a628d",
"view_tag": "a6"
}
}
}
],
"extra": [ 1, 134, 44, 242, 26, 207, 130, 130, 22, 176, 44, 123, 33, 126, 146, 233, 255, 46, 58, 222, 226, 64, 250, 215, 31, 218, 18, 20, 241, 114, 228, 132, 93, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}