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: 6279378836a8faac884c34514fe619b595d6c42abbc9f0ad1fcb9bf3d74b299e
Tx prefix hash: 2106ff6d6baf9e49a4bf497d2e1067330c137ace37c450ec86800b1fdbb347d5
Tx public key: 8e21a1a1d65b8991f05cf04a2fcee1ed203677abcf6ed28b7d9972e99e4c19db
| Timestamp: 1779881907 | Timestamp [UTC]: 2026-05-27 11:38:27 | Age [y:d:h:m:s]: 00:012:13:57:30 |
| Block: 2953 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4933 | RingCT/type: yes/0 |
| Extra: 018e21a1a1d65b8991f05cf04a2fcee1ed203677abcf6ed28b7d9972e99e4c19db02090000000326697be300 | ||
1 output(s) for total of 34.994229604739 HMNY
| stealth address | amount | amount idx | tag |
| 00: 145b91e290dfe950c1787157da31dc8380a0e49159cf3198590f723c16411b2e | 34.994229604739 | 3503 of 0 | <41> |
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": 3013,
"vin": [ {
"gen": {
"height": 2953
}
}
],
"vout": [ {
"amount": 34994229604739,
"target": {
"tagged_key": {
"key": "145b91e290dfe950c1787157da31dc8380a0e49159cf3198590f723c16411b2e",
"view_tag": "41"
}
}
}
],
"extra": [ 1, 142, 33, 161, 161, 214, 91, 137, 145, 240, 92, 240, 74, 47, 206, 225, 237, 32, 54, 119, 171, 207, 110, 210, 139, 125, 153, 114, 233, 158, 76, 25, 219, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}