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: a2b4d4614de228c7cb63a7c8abd35dc6ebddaa3ed635ae3dcd45c84a0e666ff3
Tx prefix hash: febe3f9739d241d7002b08ad92f011f4d4721c8d2282049fe97eb0fa109f8228
Tx public key: 191a35f2ee7baf6628bba47ecef1131452117a8fe05eac36dd77f3d324c7c608
| Timestamp: 1779783931 | Timestamp [UTC]: 2026-05-26 08:25:31 | Age [y:d:h:m:s]: 00:018:02:36:45 |
| Block: 2141 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6604 | RingCT/type: yes/0 |
| Extra: 01191a35f2ee7baf6628bba47ecef1131452117a8fe05eac36dd77f3d324c7c60802090000000326697be300 | ||
1 output(s) for total of 35.041051679612 HMNY
| stealth address | amount | amount idx | tag |
| 00: b23dde280daf558fa7e87f644bd088ce91a9dbc46aab0a0699984a6af76715d3 | 35.041051679612 | 2469 of 0 | <2d> |
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": 2201,
"vin": [ {
"gen": {
"height": 2141
}
}
],
"vout": [ {
"amount": 35041051679612,
"target": {
"tagged_key": {
"key": "b23dde280daf558fa7e87f644bd088ce91a9dbc46aab0a0699984a6af76715d3",
"view_tag": "2d"
}
}
}
],
"extra": [ 1, 25, 26, 53, 242, 238, 123, 175, 102, 40, 187, 164, 126, 206, 241, 19, 20, 82, 17, 122, 143, 224, 94, 172, 54, 221, 119, 243, 211, 36, 199, 198, 8, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}