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: 7b0aa8e04b0d0d09e753bffe2b8051e32ec2849939067922bf3687ca9558a2bf
Tx prefix hash: 27bead92de220860d479b5fdada7cd4795c6b71ed3d615b830b5fb1fca72385a
Tx public key: ad13ffb5cf56d5e4cb57f2d25e5fa050a6187c9b7e8b863d2c25fbfa53344b11
| Timestamp: 1780050066 | Timestamp [UTC]: 2026-05-29 10:21:06 | Age [y:d:h:m:s]: 00:010:16:19:30 |
| Block: 4384 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3512 | RingCT/type: yes/0 |
| Extra: 01ad13ffb5cf56d5e4cb57f2d25e5fa050a6187c9b7e8b863d2c25fbfa53344b1102090000000526697be300 | ||
1 output(s) for total of 34.891459724975 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3e399209ca7682e1479f1d5b0d44f567339a4963bb488ced4152bee76f45f53e | 34.891459724975 | 5485 of 0 | <80> |
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": 4444,
"vin": [ {
"gen": {
"height": 4384
}
}
],
"vout": [ {
"amount": 34891459724975,
"target": {
"tagged_key": {
"key": "3e399209ca7682e1479f1d5b0d44f567339a4963bb488ced4152bee76f45f53e",
"view_tag": "80"
}
}
}
],
"extra": [ 1, 173, 19, 255, 181, 207, 86, 213, 228, 203, 87, 242, 210, 94, 95, 160, 80, 166, 24, 124, 155, 126, 139, 134, 61, 44, 37, 251, 250, 83, 52, 75, 17, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}