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: d4c86473f37bd273fc2014c32b856cbdb54d038f6c1abacce9c52865fe81b2e5
Tx prefix hash: 7cb854f12ea89fd5f0fd561a442e4b591aa3fadd1cd44ab9c24e119950e00940
Tx public key: 16e4bc84b88a4b1da6ae4729c8a6cf4d440b64a7ae3faf60813b096780ff2d7e
| Timestamp: 1779635484 | Timestamp [UTC]: 2026-05-24 15:11:24 | Age [y:d:h:m:s]: 00:023:17:17:48 |
| Block: 1081 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7664 | RingCT/type: yes/0 |
| Extra: 0116e4bc84b88a4b1da6ae4729c8a6cf4d440b64a7ae3faf60813b096780ff2d7e020900000002ba6d17be00 | ||
1 output(s) for total of 35.111969045216 HMNY
| stealth address | amount | amount idx | tag |
| 00: f19333f2fa7ab3587245ae14bc46ef4c969c09af4699d8d1795973a1cb8aa6b0 | 35.111969045216 | 1221 of 0 | <90> |
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": 1141,
"vin": [ {
"gen": {
"height": 1081
}
}
],
"vout": [ {
"amount": 35111969045216,
"target": {
"tagged_key": {
"key": "f19333f2fa7ab3587245ae14bc46ef4c969c09af4699d8d1795973a1cb8aa6b0",
"view_tag": "90"
}
}
}
],
"extra": [ 1, 22, 228, 188, 132, 184, 138, 75, 29, 166, 174, 71, 41, 200, 166, 207, 77, 68, 11, 100, 167, 174, 63, 175, 96, 129, 59, 9, 103, 128, 255, 45, 126, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}