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: eaf53572929268a32ecc7196dc938c36f17d549bf8b41024a511631fc391daf5
Tx prefix hash: f5e9014089f17e441aa4a8a8e2cd4d2cd289009de4863e968ddf5af634be6cb1
Tx public key: 1ab73dd08047ecd8d05a025a5924736f6d3a526a6c5eef08194f7d9d704735c7
| Timestamp: 1780758050 | Timestamp [UTC]: 2026-06-06 15:00:50 | Age [y:d:h:m:s]: 00:002:09:45:57 |
| Block: 6549 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1337 | RingCT/type: yes/0 |
| Extra: 011ab73dd08047ecd8d05a025a5924736f6d3a526a6c5eef08194f7d9d704735c7020900000001e49593ff00 | ||
1 output(s) for total of 34.752693928726 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0fbab4612a457f0e5233a24e262c2682421ac6b28ad41860398cbfde6f3a7514 | 34.752693928726 | 8059 of 0 | <9d> |
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": 6609,
"vin": [ {
"gen": {
"height": 6549
}
}
],
"vout": [ {
"amount": 34752693928726,
"target": {
"tagged_key": {
"key": "0fbab4612a457f0e5233a24e262c2682421ac6b28ad41860398cbfde6f3a7514",
"view_tag": "9d"
}
}
}
],
"extra": [ 1, 26, 183, 61, 208, 128, 71, 236, 216, 208, 90, 2, 90, 89, 36, 115, 111, 109, 58, 82, 106, 108, 94, 239, 8, 25, 79, 125, 157, 112, 71, 53, 199, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}