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: eba57a190c0177090be0fb2791173f904c1ba0936130b20ee2d517b9c6478f68
Tx prefix hash: eb758320f0d1e6d55cfdc184b756def0ae71dd94d67c8f976f245249dac3a497
Tx public key: fca8824c36e013856cd322885868045c4d49b4900aee46429d46f046ea1c867d
| Timestamp: 1780779671 | Timestamp [UTC]: 2026-06-06 21:01:11 | Age [y:d:h:m:s]: 00:002:05:48:37 |
| Block: 6756 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1144 | RingCT/type: yes/0 |
| Extra: 01fca8824c36e013856cd322885868045c4d49b4900aee46429d46f046ea1c867d020900000001e49593ff00 | ||
1 output(s) for total of 34.733959105788 HMNY
| stealth address | amount | amount idx | tag |
| 00: 912b43f72dce67d3f53591e954000491c2adaddd1dc4bffd29fb7fdf118bc95c | 34.733959105788 | 8338 of 0 | <55> |
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": 6816,
"vin": [ {
"gen": {
"height": 6756
}
}
],
"vout": [ {
"amount": 34733959105788,
"target": {
"tagged_key": {
"key": "912b43f72dce67d3f53591e954000491c2adaddd1dc4bffd29fb7fdf118bc95c",
"view_tag": "55"
}
}
}
],
"extra": [ 1, 252, 168, 130, 76, 54, 224, 19, 133, 108, 211, 34, 136, 88, 104, 4, 92, 77, 73, 180, 144, 10, 238, 70, 66, 157, 70, 240, 70, 234, 28, 134, 125, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}