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: b4cdac5522a1394ea7a683693d154220ed7640f7a89656551c3b8d2584358fa8
Tx prefix hash: 5e95d7804af6500231d14f5d96cefe5309b366ab064230750492256e82be2926
Tx public key: 3b1a06e422cebbe5504d9d5dbf0b055313a550d617a30f7ebde9f9ab1b926bda
| Timestamp: 1779854761 | Timestamp [UTC]: 2026-05-27 04:06:01 | Age [y:d:h:m:s]: 00:012:21:29:56 |
| Block: 2600 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5286 | RingCT/type: yes/0 |
| Extra: 013b1a06e422cebbe5504d9d5dbf0b055313a550d617a30f7ebde9f9ab1b926bda02090000000126697be300 | ||
1 output(s) for total of 35.010387579699 HMNY
| stealth address | amount | amount idx | tag |
| 00: d6cf7bb73a3ae053caff6f8f23f675d0ad7100facbf948d2364c31c6b71cba53 | 35.010387579699 | 3060 of 0 | <67> |
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": 2660,
"vin": [ {
"gen": {
"height": 2600
}
}
],
"vout": [ {
"amount": 35010387579699,
"target": {
"tagged_key": {
"key": "d6cf7bb73a3ae053caff6f8f23f675d0ad7100facbf948d2364c31c6b71cba53",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 59, 26, 6, 228, 34, 206, 187, 229, 80, 77, 157, 93, 191, 11, 5, 83, 19, 165, 80, 214, 23, 163, 15, 126, 189, 233, 249, 171, 27, 146, 107, 218, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}