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: 73940632e8e2415104a442f9b88f8153f973c04803b86807791ce7a8764c495e
Tx prefix hash: 4a29c4fd8221015aa4c9dcae2fe839df41bb3751682a9b98986a900289638973
Tx public key: d06ea67c984c3ceaec2aee18135ff3496ea3421a43e3045c29c0d75f848c5f4d
| Timestamp: 1779903807 | Timestamp [UTC]: 2026-05-27 17:43:27 | Age [y:d:h:m:s]: 00:012:05:35:26 |
| Block: 3175 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4711 | RingCT/type: yes/0 |
| Extra: 01d06ea67c984c3ceaec2aee18135ff3496ea3421a43e3045c29c0d75f848c5f4d02090000000226697be300 | ||
1 output(s) for total of 34.972011807232 HMNY
| stealth address | amount | amount idx | tag |
| 00: 716b5cc55250de46d4e46226252b20a19f1fb0b949db4a415279b59ea32546d1 | 34.972011807232 | 3799 of 0 | <26> |
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": 3235,
"vin": [ {
"gen": {
"height": 3175
}
}
],
"vout": [ {
"amount": 34972011807232,
"target": {
"tagged_key": {
"key": "716b5cc55250de46d4e46226252b20a19f1fb0b949db4a415279b59ea32546d1",
"view_tag": "26"
}
}
}
],
"extra": [ 1, 208, 110, 166, 124, 152, 76, 60, 234, 236, 42, 238, 24, 19, 95, 243, 73, 110, 163, 66, 26, 67, 227, 4, 92, 41, 192, 215, 95, 132, 140, 95, 77, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}