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: d1218301eb07e152e58f96a566b6198d03f8d88b12114a9758ca597cc736b1c4
Tx prefix hash: 0c476cadd0a823ccad39da2da1df27a3a892730fec754b912512bae36981e890
Tx public key: 6d1137b5369e298210f36610e0d131cbd3d021c5cb5e1f1be56bfc37d90190d2
| Timestamp: 1779857842 | Timestamp [UTC]: 2026-05-27 04:57:22 | Age [y:d:h:m:s]: 00:012:22:53:36 |
| Block: 2638 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5328 | RingCT/type: yes/0 |
| Extra: 016d1137b5369e298210f36610e0d131cbd3d021c5cb5e1f1be56bfc37d90190d202090000000226697be300 | ||
1 output(s) for total of 35.007850142670 HMNY
| stealth address | amount | amount idx | tag |
| 00: a3741e0c82638b1d284b2e31929df5d8bf354cf2de4c88727387053604994ea7 | 35.007850142670 | 3108 of 0 | <78> |
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": 2698,
"vin": [ {
"gen": {
"height": 2638
}
}
],
"vout": [ {
"amount": 35007850142670,
"target": {
"tagged_key": {
"key": "a3741e0c82638b1d284b2e31929df5d8bf354cf2de4c88727387053604994ea7",
"view_tag": "78"
}
}
}
],
"extra": [ 1, 109, 17, 55, 181, 54, 158, 41, 130, 16, 243, 102, 16, 224, 209, 49, 203, 211, 208, 33, 197, 203, 94, 31, 27, 229, 107, 252, 55, 217, 1, 144, 210, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}