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: 1bf72b604e9d33bb2c06a41fa65f19cda0a3514d7e922950b83026a15e79c8fe
Tx prefix hash: 9282f5f1f592a944d85354cced8d881b49759d4f209c70a6820b716e97303099
Tx public key: f45e6ed039a148afbec9d590ae60207d0452e22ab56c4ad4c00ca790038cabb8
| Timestamp: 1780747640 | Timestamp [UTC]: 2026-06-06 12:07:20 | Age [y:d:h:m:s]: 00:010:20:14:59 |
| Block: 6461 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2284 | RingCT/type: yes/0 |
| Extra: 01f45e6ed039a148afbec9d590ae60207d0452e22ab56c4ad4c00ca790038cabb8020900000002e49593ff00 | ||
1 output(s) for total of 34.753508305745 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0a8f746f54a91f9b78c3c6ae2e4e7e6ff0d1a29b8b5146da09697279be1a39f2 | 34.753508305745 | 7956 of 0 | <50> |
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": 6521,
"vin": [ {
"gen": {
"height": 6461
}
}
],
"vout": [ {
"amount": 34753508305745,
"target": {
"tagged_key": {
"key": "0a8f746f54a91f9b78c3c6ae2e4e7e6ff0d1a29b8b5146da09697279be1a39f2",
"view_tag": "50"
}
}
}
],
"extra": [ 1, 244, 94, 110, 208, 57, 161, 72, 175, 190, 201, 213, 144, 174, 96, 32, 125, 4, 82, 226, 42, 181, 108, 74, 212, 192, 12, 167, 144, 3, 140, 171, 184, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}