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: 7f9e68b53e4cf082ad192c59e59c889f9d76d785460ef049b525aeaefe064b69
Tx prefix hash: 2affbd2378e68ab3d732c1611c5e3b2d38460ff317f2a0c788b7b0c550697072
Tx public key: 97993a6d9eaf4e86b11c42b73f9818e9d49faa524eeec304a757eadff82359c3
| Timestamp: 1780323332 | Timestamp [UTC]: 2026-06-01 14:15:32 | Age [y:d:h:m:s]: 00:007:12:25:04 |
| Block: 5109 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2788 | RingCT/type: yes/0 |
| Extra: 0197993a6d9eaf4e86b11c42b73f9818e9d49faa524eeec304a757eadff82359c302090000002a26697be300 | ||
1 output(s) for total of 34.843244144545 HMNY
| stealth address | amount | amount idx | tag |
| 00: e409f7e525c86b4fbf09d6fb0a85a251526516fcb141d19aa7a5d56bc5389664 | 34.843244144545 | 6484 of 0 | <78> |
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": 5169,
"vin": [ {
"gen": {
"height": 5109
}
}
],
"vout": [ {
"amount": 34843244144545,
"target": {
"tagged_key": {
"key": "e409f7e525c86b4fbf09d6fb0a85a251526516fcb141d19aa7a5d56bc5389664",
"view_tag": "78"
}
}
}
],
"extra": [ 1, 151, 153, 58, 109, 158, 175, 78, 134, 177, 28, 66, 183, 63, 152, 24, 233, 212, 159, 170, 82, 78, 238, 195, 4, 167, 87, 234, 223, 248, 35, 89, 195, 2, 9, 0, 0, 0, 42, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}