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: df3aab7b3b1303e058705e03fab79162961e490981e23543b4f2c20ee8d893c1
Tx prefix hash: 322964583d436e15ead643430e4c09ad048ef830cece89a5099af84d72cdbc8f
Tx public key: cf45c5894151a748a0cb0f74d11b793c6ccc61046d15b336d166f0e50487936a
| Timestamp: 1780061543 | Timestamp [UTC]: 2026-05-29 13:32:23 | Age [y:d:h:m:s]: 00:010:13:17:25 |
| Block: 4528 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3392 | RingCT/type: yes/0 |
| Extra: 01cf45c5894151a748a0cb0f74d11b793c6ccc61046d15b336d166f0e50487936a02090000000326697be300 | ||
1 output(s) for total of 34.881877806141 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3c2d03123625025f03ef1cda7d817c4a4c12073d1f08c9bc8ca0a972bb0897a3 | 34.881877806141 | 5679 of 0 | <fb> |
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": 4588,
"vin": [ {
"gen": {
"height": 4528
}
}
],
"vout": [ {
"amount": 34881877806141,
"target": {
"tagged_key": {
"key": "3c2d03123625025f03ef1cda7d817c4a4c12073d1f08c9bc8ca0a972bb0897a3",
"view_tag": "fb"
}
}
}
],
"extra": [ 1, 207, 69, 197, 137, 65, 81, 167, 72, 160, 203, 15, 116, 209, 27, 121, 60, 108, 204, 97, 4, 109, 21, 179, 54, 209, 102, 240, 229, 4, 135, 147, 106, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}