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: b54e2b8ebbedc46af5d7c391865d5c642e9d89ddc66de93b7b944b0c3e41c4bf
Tx prefix hash: 6fa3628814fa8794f1b077e6bbc59037df538a9051b1f79474994b3acd00d8c5
Tx public key: 58c7cf42d2aedd7d182e61328951bdcc1addc1087c1201d2d9b203860e92c3eb
| Timestamp: 1780730367 | Timestamp [UTC]: 2026-06-06 07:19:27 | Age [y:d:h:m:s]: 00:002:18:16:30 |
| Block: 6309 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1577 | RingCT/type: yes/0 |
| Extra: 0158c7cf42d2aedd7d182e61328951bdcc1addc1087c1201d2d9b203860e92c3eb020900000002e49593ff00 | ||
1 output(s) for total of 34.763585408643 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7b3f44ffbb7d927fa039ab3a4cb974b7256df1af79e8211dcde04de77e1a8eff | 34.763585408643 | 7794 of 0 | <48> |
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": 6369,
"vin": [ {
"gen": {
"height": 6309
}
}
],
"vout": [ {
"amount": 34763585408643,
"target": {
"tagged_key": {
"key": "7b3f44ffbb7d927fa039ab3a4cb974b7256df1af79e8211dcde04de77e1a8eff",
"view_tag": "48"
}
}
}
],
"extra": [ 1, 88, 199, 207, 66, 210, 174, 221, 125, 24, 46, 97, 50, 137, 81, 189, 204, 26, 221, 193, 8, 124, 18, 1, 210, 217, 178, 3, 134, 14, 146, 195, 235, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}