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: 85672b92c70cc69c2d7d31c542eccf9db4114c6f2436958c950396374bbd1bde
Tx prefix hash: e4360c902fc1a72eae8791fe7db06d1aef71203cfdae91cb9c2e1d81bdb3b7b3
Tx public key: bdf1589755c5486457154e973ca2e5a4354567dea9f4a372cb9f111af429ca6e
| Timestamp: 1779764707 | Timestamp [UTC]: 2026-05-26 03:05:07 | Age [y:d:h:m:s]: 00:022:05:24:05 |
| Block: 1956 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6789 | RingCT/type: yes/0 |
| Extra: 01bdf1589755c5486457154e973ca2e5a4354567dea9f4a372cb9f111af429ca6e02090000000626697be300 | ||
1 output(s) for total of 35.053418441015 HMNY
| stealth address | amount | amount idx | tag |
| 00: 58c8e21bc17d175e436b723c925cf2d697cd44db2a592fae150ba6ed20d57146 | 35.053418441015 | 2220 of 0 | <86> |
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": 2016,
"vin": [ {
"gen": {
"height": 1956
}
}
],
"vout": [ {
"amount": 35053418441015,
"target": {
"tagged_key": {
"key": "58c8e21bc17d175e436b723c925cf2d697cd44db2a592fae150ba6ed20d57146",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 189, 241, 88, 151, 85, 197, 72, 100, 87, 21, 78, 151, 60, 162, 229, 164, 53, 69, 103, 222, 169, 244, 163, 114, 203, 159, 17, 26, 244, 41, 202, 110, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}