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: de7f9e628c90bb6e955dc41dd94181508098d17902ae245a96d5ed15be7b22de
Tx prefix hash: 238c0bf973f123bc2329de81bfce88ea5b3eba3200d13640501c0f1d75a48700
Tx public key: ed6e5040cd0c88fd714e9c6b3f2ab3f2e1d40ced9a01cfa48826ba4f97a4db73
| Timestamp: 1779456221 | Timestamp [UTC]: 2026-05-22 13:23:41 | Age [y:d:h:m:s]: 00:017:11:23:06 |
| Block: 386 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7500 | RingCT/type: yes/0 |
| Extra: 01ed6e5040cd0c88fd714e9c6b3f2ab3f2e1d40ced9a01cfa48826ba4f97a4db7302090000000193369e7d00 | ||
1 output(s) for total of 35.173008235762 HMNY
| stealth address | amount | amount idx | tag |
| 00: bb1585217ff88863656cb227b6ee7aa33d4827913212fc58a3d536f2b6df25fe | 35.173008235762 | 384 of 0 | <1f> |
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": 446,
"vin": [ {
"gen": {
"height": 386
}
}
],
"vout": [ {
"amount": 35173008235762,
"target": {
"tagged_key": {
"key": "bb1585217ff88863656cb227b6ee7aa33d4827913212fc58a3d536f2b6df25fe",
"view_tag": "1f"
}
}
}
],
"extra": [ 1, 237, 110, 80, 64, 205, 12, 136, 253, 113, 78, 156, 107, 63, 42, 179, 242, 225, 212, 12, 237, 154, 1, 207, 164, 136, 38, 186, 79, 151, 164, 219, 115, 2, 9, 0, 0, 0, 1, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}