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: 8989479215b5da1ac211393a2e245205e8c9d5f17d1974bdbf5dd9f81021bde7
Tx prefix hash: fd787ebed3f25ce4fece7501236e82df2bb39a8f2493c7ad8e57adb9d5445bea
Tx public key: 1821329723f01ac28992c0b98913109fe3c3fbf5a89989898b89395e7b5a54a4
| Timestamp: 1780974033 | Timestamp [UTC]: 2026-06-09 03:00:33 | Age [y:d:h:m:s]: 00:000:09:37:12 |
| Block: 7911 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 661 | RingCT/type: yes/0 |
| Extra: 011821329723f01ac28992c0b98913109fe3c3fbf5a89989898b89395e7b5a54a4020900000001e49593ff00 | ||
1 output(s) for total of 34.672957972082 HMNY
| stealth address | amount | amount idx | tag |
| 00: b7d5812017b4a2e2f277d4843a800fba7a8304f5b583bf9292b76c1ce3040c91 | 34.672957972082 | 9809 of 0 | <8f> |
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": 7971,
"vin": [ {
"gen": {
"height": 7911
}
}
],
"vout": [ {
"amount": 34672957972082,
"target": {
"tagged_key": {
"key": "b7d5812017b4a2e2f277d4843a800fba7a8304f5b583bf9292b76c1ce3040c91",
"view_tag": "8f"
}
}
}
],
"extra": [ 1, 24, 33, 50, 151, 35, 240, 26, 194, 137, 146, 192, 185, 137, 19, 16, 159, 227, 195, 251, 245, 168, 153, 137, 137, 139, 137, 57, 94, 123, 90, 84, 164, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}