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: 564afef31e490099bef1a86e8d202b1d1312ee82175d3a421b175eabc39c779e
Tx prefix hash: 5015259f2f8e2c2d7d3e0e97fff43d6811549cd50f18541fdf968aab0f0b487b
Tx public key: d85925f75744ed4bf562d6060769b5951d74519749b20aa83c6be212df594447
| Timestamp: 1780982609 | Timestamp [UTC]: 2026-06-09 05:23:29 | Age [y:d:h:m:s]: 00:000:10:36:15 |
| Block: 8067 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 624 | RingCT/type: yes/0 |
| Extra: 01d85925f75744ed4bf562d6060769b5951d74519749b20aa83c6be212df594447020900000001e49593ff00 | ||
1 output(s) for total of 34.647214075012 HMNY
| stealth address | amount | amount idx | tag |
| 00: 41f7dd2baaeae3373b16e6743074cdbc8688b0fbd5923e51b15dfa898fa68b6d | 34.647214075012 | 9997 of 0 | <4e> |
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": 8127,
"vin": [ {
"gen": {
"height": 8067
}
}
],
"vout": [ {
"amount": 34647214075012,
"target": {
"tagged_key": {
"key": "41f7dd2baaeae3373b16e6743074cdbc8688b0fbd5923e51b15dfa898fa68b6d",
"view_tag": "4e"
}
}
}
],
"extra": [ 1, 216, 89, 37, 247, 87, 68, 237, 75, 245, 98, 214, 6, 7, 105, 181, 149, 29, 116, 81, 151, 73, 178, 10, 168, 60, 107, 226, 18, 223, 89, 68, 71, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}