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: a39fbd718c9c3221fa8da81efdfd1c0a8d2faba7643c8fb063e38a9619c3dd96
Tx prefix hash: 4cd502325a7c4a294d8c791bb00b3ce64b8692463eb66ce676a061804f65fb03
Tx public key: 5e7d374a27c98ee3f90cc1c2772943b9708f5c41709dcab805fa7662e86063b7
| Timestamp: 1779849870 | Timestamp [UTC]: 2026-05-27 02:44:30 | Age [y:d:h:m:s]: 00:017:08:17:46 |
| Block: 2515 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6230 | RingCT/type: yes/0 |
| Extra: 015e7d374a27c98ee3f90cc1c2772943b9708f5c41709dcab805fa7662e86063b702090000000426697be300 | ||
1 output(s) for total of 35.016064091516 HMNY
| stealth address | amount | amount idx | tag |
| 00: 075d51fe611a0f089fbe5d7bafc5aa02e006af3de352eedbe558e47025cb44d2 | 35.016064091516 | 2959 of 0 | <5d> |
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": 2575,
"vin": [ {
"gen": {
"height": 2515
}
}
],
"vout": [ {
"amount": 35016064091516,
"target": {
"tagged_key": {
"key": "075d51fe611a0f089fbe5d7bafc5aa02e006af3de352eedbe558e47025cb44d2",
"view_tag": "5d"
}
}
}
],
"extra": [ 1, 94, 125, 55, 74, 39, 201, 142, 227, 249, 12, 193, 194, 119, 41, 67, 185, 112, 143, 92, 65, 112, 157, 202, 184, 5, 250, 118, 98, 232, 96, 99, 183, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}