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: 0f523924e78dc3245b99afb1e89a69fc92c07c09b3ef2e4a3fcfeb87729c0d7c
Tx prefix hash: ddc259ffa7d5a259ab427bb92125afd30ec1deb8db0211f33f7b2952dd211f9f
Tx public key: 3f1f6a42121cf386b4451cbdd350bb3c36fb0f53ec68a692c876a08f842d4c57
| Timestamp: 1779713802 | Timestamp [UTC]: 2026-05-25 12:56:42 | Age [y:d:h:m:s]: 00:014:15:36:20 |
| Block: 1604 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6423 | RingCT/type: yes/0 |
| Extra: 013f1f6a42121cf386b4451cbdd350bb3c36fb0f53ec68a692c876a08f842d4c57020900000002ba6d17be00 | ||
1 output(s) for total of 35.076960765172 HMNY
| stealth address | amount | amount idx | tag |
| 00: a970fff3b1c22da5cc68b1be1780c8785c0b7e53f3cdb44697b219b5ba2e05c6 | 35.076960765172 | 1762 of 0 | <f6> |
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": 1664,
"vin": [ {
"gen": {
"height": 1604
}
}
],
"vout": [ {
"amount": 35076960765172,
"target": {
"tagged_key": {
"key": "a970fff3b1c22da5cc68b1be1780c8785c0b7e53f3cdb44697b219b5ba2e05c6",
"view_tag": "f6"
}
}
}
],
"extra": [ 1, 63, 31, 106, 66, 18, 28, 243, 134, 180, 69, 28, 189, 211, 80, 187, 60, 54, 251, 15, 83, 236, 104, 166, 146, 200, 118, 160, 143, 132, 45, 76, 87, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}