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: 1e4a86ecc7ea946677ea1c39606650cab90e0ac44bd22b36ae3a52ae4f896188
Tx prefix hash: 88fb3fe50963e14018e3092a48c264514d4b585c7f2ae5631063052914c795c7
Tx public key: 2cfaa49bf6244d6487fed9aa77767b86969f2170457e957cfc54abce1d1ceca1
| Timestamp: 1780051664 | Timestamp [UTC]: 2026-05-29 10:47:44 | Age [y:d:h:m:s]: 00:010:14:48:13 |
| Block: 4405 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3481 | RingCT/type: yes/0 |
| Extra: 012cfaa49bf6244d6487fed9aa77767b86969f2170457e957cfc54abce1d1ceca102090000000326697be300 | ||
1 output(s) for total of 34.890062197893 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2e23fd7680f8365823658daa475f31cac3f678936a0f0ed7cd9603cd397a93d4 | 34.890062197893 | 5510 of 0 | <a1> |
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": 4465,
"vin": [ {
"gen": {
"height": 4405
}
}
],
"vout": [ {
"amount": 34890062197893,
"target": {
"tagged_key": {
"key": "2e23fd7680f8365823658daa475f31cac3f678936a0f0ed7cd9603cd397a93d4",
"view_tag": "a1"
}
}
}
],
"extra": [ 1, 44, 250, 164, 155, 246, 36, 77, 100, 135, 254, 217, 170, 119, 118, 123, 134, 150, 159, 33, 112, 69, 126, 149, 124, 252, 84, 171, 206, 29, 28, 236, 161, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}