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: 38f89233ef4074f3f27fd29162919ed607fb6d50a7a7184ee88772b99aa6d1a6
Tx prefix hash: a311ead4a9579305f11847886aa0f6c4d93abcf311cff2ad39a51c716f6a66c9
Tx public key: d2b779bf38d6175b031cc93afb6769dd44b048df4880850047be8e86906bfd50
| Timestamp: 1780988775 | Timestamp [UTC]: 2026-06-09 07:06:15 | Age [y:d:h:m:s]: 00:000:08:53:29 |
| Block: 8189 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 502 | RingCT/type: yes/0 |
| Extra: 01d2b779bf38d6175b031cc93afb6769dd44b048df4880850047be8e86906bfd50020900000001e49593ff00 | ||
1 output(s) for total of 34.639152718685 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7be47861b57dff9cbea27739c3f301c1b17d04101a2df260012f51c4e5ea518e | 34.639152718685 | 10139 of 0 | <b3> |
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": 8249,
"vin": [ {
"gen": {
"height": 8189
}
}
],
"vout": [ {
"amount": 34639152718685,
"target": {
"tagged_key": {
"key": "7be47861b57dff9cbea27739c3f301c1b17d04101a2df260012f51c4e5ea518e",
"view_tag": "b3"
}
}
}
],
"extra": [ 1, 210, 183, 121, 191, 56, 214, 23, 91, 3, 28, 201, 58, 251, 103, 105, 221, 68, 176, 72, 223, 72, 128, 133, 0, 71, 190, 142, 134, 144, 107, 253, 80, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}