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: 5fd001365b65b16afdde46e4b83a53583434b74bea013426cd1bbe7a7c6bb29e
Tx prefix hash: f67210c9081eae6cfa487f8bc4c06e4b7fdbdee74ce323ce19fce5b1ddfd0097
Tx public key: f6f439b9fb24ecfbb8d0ece4a30db8a4ca640a739727185f08b0a40e06250113
| Timestamp: 1780865224 | Timestamp [UTC]: 2026-06-07 20:47:04 | Age [y:d:h:m:s]: 00:001:02:31:49 |
| Block: 7656 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 230 | RingCT/type: yes/0 |
| Extra: 01f6f439b9fb24ecfbb8d0ece4a30db8a4ca640a739727185f08b0a40e06250113020900000002e49593ff00 | ||
1 output(s) for total of 34.674385403650 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4cd49dc4bd009ef1747a31a1776b481acc35a5f36495fc46b6d78801f77d2e99 | 34.674385403650 | 9466 of 0 | <8d> |
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": 7716,
"vin": [ {
"gen": {
"height": 7656
}
}
],
"vout": [ {
"amount": 34674385403650,
"target": {
"tagged_key": {
"key": "4cd49dc4bd009ef1747a31a1776b481acc35a5f36495fc46b6d78801f77d2e99",
"view_tag": "8d"
}
}
}
],
"extra": [ 1, 246, 244, 57, 185, 251, 36, 236, 251, 184, 208, 236, 228, 163, 13, 184, 164, 202, 100, 10, 115, 151, 39, 24, 95, 8, 176, 164, 14, 6, 37, 1, 19, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}