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: 94bb054efdc587f466d6ebfdf7872ccf2a680d2f2fd561023f6236e532cea2cc
Tx prefix hash: e42d378f140de2f2cbdfe8eb7894d9dea2f355bbeb84e92bd2603704a47e5b8b
Tx public key: 08dc8b8073baa2905268e51775066b6e38d1b26c3259c4315b09e0f2c7108bde
| Timestamp: 1779895209 | Timestamp [UTC]: 2026-05-27 15:20:09 | Age [y:d:h:m:s]: 00:013:01:48:54 |
| Block: 3100 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5634 | RingCT/type: yes/0 |
| Extra: 0108dc8b8073baa2905268e51775066b6e38d1b26c3259c4315b09e0f2c7108bde02090000000226697be300 | ||
1 output(s) for total of 34.977014956266 HMNY
| stealth address | amount | amount idx | tag |
| 00: baa462f421c418e96bc113871841395ca74739b77d40f53aadedbf874bd22ae1 | 34.977014956266 | 3696 of 0 | <59> |
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": 3160,
"vin": [ {
"gen": {
"height": 3100
}
}
],
"vout": [ {
"amount": 34977014956266,
"target": {
"tagged_key": {
"key": "baa462f421c418e96bc113871841395ca74739b77d40f53aadedbf874bd22ae1",
"view_tag": "59"
}
}
}
],
"extra": [ 1, 8, 220, 139, 128, 115, 186, 162, 144, 82, 104, 229, 23, 117, 6, 107, 110, 56, 209, 178, 108, 50, 89, 196, 49, 91, 9, 224, 242, 199, 16, 139, 222, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}