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: e3f9e7d1b3663a9924456d2dd036f3545b84aaae88f8c5674cfc28ef6e4128b6
Tx prefix hash: 85f9fa8ffb64625fa7596090430f6dff91b4faf4b1c637359e01aa27517aecdf
Tx public key: a3e692174b2d6884ab7dc4a5e112af2f80a3d1c193b9327919179326fa9d5ed4
| Timestamp: 1780063020 | Timestamp [UTC]: 2026-05-29 13:57:00 | Age [y:d:h:m:s]: 00:010:11:38:57 |
| Block: 4548 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3338 | RingCT/type: yes/0 |
| Extra: 01a3e692174b2d6884ab7dc4a5e112af2f80a3d1c193b9327919179326fa9d5ed402090000000226697be300 | ||
1 output(s) for total of 34.880547192213 HMNY
| stealth address | amount | amount idx | tag |
| 00: eede7c673daacc5a8e41fbbbcd04546efadba76b41502a0deb1f0e4c897cc5ec | 34.880547192213 | 5706 of 0 | <bb> |
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": 4608,
"vin": [ {
"gen": {
"height": 4548
}
}
],
"vout": [ {
"amount": 34880547192213,
"target": {
"tagged_key": {
"key": "eede7c673daacc5a8e41fbbbcd04546efadba76b41502a0deb1f0e4c897cc5ec",
"view_tag": "bb"
}
}
}
],
"extra": [ 1, 163, 230, 146, 23, 75, 45, 104, 132, 171, 125, 196, 165, 225, 18, 175, 47, 128, 163, 209, 193, 147, 185, 50, 121, 25, 23, 147, 38, 250, 157, 94, 212, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}