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: f029af64f6f773067d0d778ec0445e2fa028cdffe9ee1b22122453c25178964e
Tx prefix hash: 31a4e41dada06a1af554859d511e402c7336d5c2f2ae5a9d39b5a60dd9bb5b2b
Tx public key: 42634d95d8e4bd1358b4670ea7ccb166a68cf3b75b115a946742767ae3eb09cf
| Timestamp: 1780686732 | Timestamp [UTC]: 2026-06-05 19:12:12 | Age [y:d:h:m:s]: 00:003:06:23:45 |
| Block: 5444 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2442 | RingCT/type: yes/0 |
| Extra: 0142634d95d8e4bd1358b4670ea7ccb166a68cf3b75b115a946742767ae3eb09cf020900000002e49593ff00 | ||
1 output(s) for total of 34.820987732858 HMNY
| stealth address | amount | amount idx | tag |
| 00: cbe718a084e86543e729d1f6b878edf00340893b8796a93dc2809816651146b9 | 34.820987732858 | 6883 of 0 | <8b> |
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": 5504,
"vin": [ {
"gen": {
"height": 5444
}
}
],
"vout": [ {
"amount": 34820987732858,
"target": {
"tagged_key": {
"key": "cbe718a084e86543e729d1f6b878edf00340893b8796a93dc2809816651146b9",
"view_tag": "8b"
}
}
}
],
"extra": [ 1, 66, 99, 77, 149, 216, 228, 189, 19, 88, 180, 103, 14, 167, 204, 177, 102, 166, 140, 243, 183, 91, 17, 90, 148, 103, 66, 118, 122, 227, 235, 9, 207, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}