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: bcb2b3918c4de23bb9827d5df7f89d23c6b64b600c5a59734f49e8e43d06afd4
Tx prefix hash: ff25fe22c9f434b62ab2b0feedca48bcd6db70fcc6ca80ff795237261c3c69be
Tx public key: b6a7225f73238596db6a3158723f0a2b2ca27169568343d493069d4029df5c1e
| Timestamp: 1780815125 | Timestamp [UTC]: 2026-06-07 06:52:05 | Age [y:d:h:m:s]: 00:001:17:54:42 |
| Block: 7051 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 835 | RingCT/type: yes/0 |
| Extra: 01b6a7225f73238596db6a3158723f0a2b2ca27169568343d493069d4029df5c1e020900000002e49593ff00 | ||
1 output(s) for total of 34.714420902453 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7d6493681db0b20c7cfced52695a2739cc38dae2a219470bf4fd01a11468e40d | 34.714420902453 | 8695 of 0 | <be> |
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": 7111,
"vin": [ {
"gen": {
"height": 7051
}
}
],
"vout": [ {
"amount": 34714420902453,
"target": {
"tagged_key": {
"key": "7d6493681db0b20c7cfced52695a2739cc38dae2a219470bf4fd01a11468e40d",
"view_tag": "be"
}
}
}
],
"extra": [ 1, 182, 167, 34, 95, 115, 35, 133, 150, 219, 106, 49, 88, 114, 63, 10, 43, 44, 162, 113, 105, 86, 131, 67, 212, 147, 6, 157, 64, 41, 223, 92, 30, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}