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: a54a3982376908039d1c5fb94f99fb8c3c14a442a8eb6bb90c54056454362e92
Tx prefix hash: 1ddcfb04b0334bc587afe701ce8367bcb5e5fc2b6352fa4514fe46254ece859f
Tx public key: 0127f03dba0e95c04cbc908c7e1a92dba1a734bc9b2079746f4d44adedc6d523
| Timestamp: 1780134986 | Timestamp [UTC]: 2026-05-30 09:56:26 | Age [y:d:h:m:s]: 00:009:17:54:32 |
| Block: 4957 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3009 | RingCT/type: yes/0 |
| Extra: 010127f03dba0e95c04cbc908c7e1a92dba1a734bc9b2079746f4d44adedc6d52302090000000426697be300 | ||
1 output(s) for total of 34.859164867183 HMNY
| stealth address | amount | amount idx | tag |
| 00: f25d06aa47c763d1d68574b36572586fa91608748b2a298f954f2f615b142d27 | 34.859164867183 | 6300 of 0 | <e0> |
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": 5017,
"vin": [ {
"gen": {
"height": 4957
}
}
],
"vout": [ {
"amount": 34859164867183,
"target": {
"tagged_key": {
"key": "f25d06aa47c763d1d68574b36572586fa91608748b2a298f954f2f615b142d27",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 1, 39, 240, 61, 186, 14, 149, 192, 76, 188, 144, 140, 126, 26, 146, 219, 161, 167, 52, 188, 155, 32, 121, 116, 111, 77, 68, 173, 237, 198, 213, 35, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}