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: 32175385f44f8bac3473e38727ebde3b0a7f1fa5c861d48872c9f3fb184dfca8
Tx prefix hash: 5f0e17912b520d957158d80ffb7d4c68c55a4eaeb0517d916aeff19540bd11b6
Tx public key: 99ddde4003f00ac7fa1e7529fdb988e33dcfa18946fba15b57de020d74325c75
| Timestamp: 1780690682 | Timestamp [UTC]: 2026-06-05 20:18:02 | Age [y:d:h:m:s]: 00:011:11:47:19 |
| Block: 5673 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3072 | RingCT/type: yes/0 |
| Extra: 0199ddde4003f00ac7fa1e7529fdb988e33dcfa18946fba15b57de020d74325c75020900000001e49593ff00 | ||
1 output(s) for total of 34.805781829631 HMNY
| stealth address | amount | amount idx | tag |
| 00: 050505e8b3f04df11b8e6d9035543b30d3f8e0a0ddc6894742ce365ef36d010a | 34.805781829631 | 7122 of 0 | <92> |
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": 5733,
"vin": [ {
"gen": {
"height": 5673
}
}
],
"vout": [ {
"amount": 34805781829631,
"target": {
"tagged_key": {
"key": "050505e8b3f04df11b8e6d9035543b30d3f8e0a0ddc6894742ce365ef36d010a",
"view_tag": "92"
}
}
}
],
"extra": [ 1, 153, 221, 222, 64, 3, 240, 10, 199, 250, 30, 117, 41, 253, 185, 136, 227, 61, 207, 161, 137, 70, 251, 161, 91, 87, 222, 2, 13, 116, 50, 92, 117, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}