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: a6c29c2b7424d2b803aff41a63c613fca97118f3dcce536d3965bec52c1a29c5
Tx prefix hash: 8f6d23e8c89c7fad8b6be0a97ada60062015bfaf977a603c22e013b075a6e3cd
Tx public key: a8f83937a0f0034c23f8405fd045a52fe1c44604a77ecf564c354e7f03b6c6e8
| Timestamp: 1780980580 | Timestamp [UTC]: 2026-06-09 04:49:40 | Age [y:d:h:m:s]: 00:000:04:10:19 |
| Block: 8023 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 309 | RingCT/type: yes/0 |
| Extra: 01a8f83937a0f0034c23f8405fd045a52fe1c44604a77ecf564c354e7f03b6c6e8020900000001e49593ff00 | ||
1 output(s) for total of 34.650121909723 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1da0af9e6296a161aec72165a4d0817982397f2a1948fed16bbdd1f69ae79b85 | 34.650121909723 | 9947 of 0 | <02> |
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": 8083,
"vin": [ {
"gen": {
"height": 8023
}
}
],
"vout": [ {
"amount": 34650121909723,
"target": {
"tagged_key": {
"key": "1da0af9e6296a161aec72165a4d0817982397f2a1948fed16bbdd1f69ae79b85",
"view_tag": "02"
}
}
}
],
"extra": [ 1, 168, 248, 57, 55, 160, 240, 3, 76, 35, 248, 64, 95, 208, 69, 165, 47, 225, 196, 70, 4, 167, 126, 207, 86, 76, 53, 78, 127, 3, 182, 198, 232, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}